jvzTrifork
Results
1
comments of
jvzTrifork
We ended up downgrading to version 3.4.6 which does not have this bug.