Bug 116518 - Crash when moving a window
Summary: Crash when moving a window
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.2.1 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-20 13:01 UTC by Peter Toye
Modified: 2018-03-21 10:59 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["basctl::Layout::ArrangeWindows()"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Toye 2018-03-20 13:01:21 UTC
After editing a dialog, the properties window stayed visible. When I moved it out of the way, LibO crashed. The crash report is at crashreport.libreoffice.org/stats/crash_details/16b1f96b-8401-4a33-863b-f2491e221142
Comment 1 Xisco Faulí 2018-03-20 13:35:56 UTC Comment hidden (obsolete)
Comment 2 Peter Toye 2018-03-20 15:16:51 UTC
I wish I could reproduce it quickly. Unfortunately, when a program crashes it's not always possible to remember the exact steps that made it crash. Also, it seems that the crash has lost not only all my edits (about an hours work) but also the entire dialog, so reproducing the problem will not be a trivial task, if indeed it is possible.

I would suggsst that in a future release of LibO the text of the crash report window be changed to say that it is only worth while reporting the bug if it can be reproduced. Unfortunately, by that time, the window with the crash report location in it will have disappeared..... Some thought on workflow is needed here if crashes are to be meaningfully reported and not just time-wasters, both for the reporter and for yourselves. Maybe put the text of the window into a text processor (e.g. Notepad on Windows) so that it can be quickly saved.
Comment 3 Xisco Faulí 2018-03-21 10:59:25 UTC
Looking at http://crashreport.libreoffice.org/stats/signature/basctl::Layout::ArrangeWindows(), it seems this crash is really weird to reproduce.
Closing as RESOLVED INSUFFICIENTDATA for the time being. Put it back to UNCONFIRMED if you manage to reproduce it again...