Created attachment 95247 [details] Screenshot of the corrupted application menus from Calc Sometimes, maybe every other day, LibreOffice's application menus fail to be rendered correctly after e.g. opening a new file or just window. See the attachment for an idea how it looks. If one continues to interact with the broken menus, LibreOffice will usually crash in a matter of seconds and display the Document Recovery dialog. LibreOffice 4.2.2.1 release on Windows 7 x64 Professional The computer is a dual-monitor setup, with the primary monitor on the left, from whose top-level corner the attached screenshot was taken when LibreOffice Calc was maximized there. The top border of the 2nd monitor is slightly lower than the top border of the primary monitor. Maybe this monitor setup is of significance.
Created attachment 95251 [details] Screenshot of the corrupted application menus from Calc (Try #2) Huh, the original screenshot image was uploaded as text/plain, sorry about that
Can you provide a trace for us? It's really hard for us to replicate these kinds of issues so getting a backtrace is usually needed. https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Please @eomanis, maybe resetting the user profile could help. Sometimes strange issues are solved. https://wiki.documentfoundation.org/UserProfile
@ Comment 3 / m.a.riosv: When I switched to LibreOffice 4.2.0 I dumped my old 4.1-and-before profile, so since the profile has only be "touched" by LibO 4.2.0 and 4.2.1 any kind of weird-old-data-in-profile issue seems somewhat unlikely. Anyhow, I think that updating from 4.2.0 to 4.2.1 should not break a user profile in any case, and if it does, it may be considered a bug that should be examined, even if it works correctly again if I wipe my profile. Therefore I'll keep the profile for now, also to aid in getting a trace. @ Comment 2 / Joel Madero: I will try to get a trace. It might take a while to get one, because a) this is only my PC at work and I don't have Windows 7 at home anywhere, and b) this bug is not readily reproducible for me. So the soonest I can have a trace ready, with some luck, is some time next week.
I have had WindDbg attached to LibreOffice during the whole time since my last post, but I haven't been able to reproduce and catch this issue. For now I'm marking this issue as RESOLVED-INVALID so it doesn't clutter up the list of more important stuff. I'll keep debugging, and if I do happen to get a trace of this I suppose I can re-open this bug report.
@eomanis, thanks for the effort.