I can confirm that it is fixed in current trunk, and I'm able to reliably reproduce the problem in 4.8.1 using the procedure outlined in bug #288441.
I can confirm that it is fixed in current trunk, and I'm able to reliably reproduce the problem in 4.8.1 using the procedure outlined in bug #288441.