How could un-initialization cause this behavior? I can also mention that the writing to the statusBar is activated by an event triggered by the user, and if the user doesn't trigger the event so that nothing is written to the statusBar, the bug does not appear either. I think memory corruption is more likely; any way to detect where the memory gets corrupted?