Comment 9 for bug 358173

Sorry, but I actually did a clean install of the daily build from today (4-12-09) and it appears to have resolved the problem, so I can't reproduce the issue. I'll keep an eye out for it and see if it pops back up again.