I can't reproduce this bug with 3.0.1 in a short time... Will report tommorow but I hope it is fixed.
I can't reproduce this bug with 3.0.1 in a short time...
Will report tommorow but I hope it is fixed.