Bug 101389 - Crash in: SfxWorkWindow::UpdateChildWindows_Impl()
Summary: Crash in: SfxWorkWindow::UpdateChildWindows_Impl()
Status: RESOLVED DUPLICATE of bug 100870
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.0.4 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-08 14:32 UTC by ikeamanual
Modified: 2016-08-08 15:10 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["SfxWorkWindow::UpdateChildWindows_Impl()"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ikeamanual 2016-08-08 14:32:04 UTC
This bug was filed from the crash reporting server and is br-369ae472-94d3-4610-9be6-bd97f72f3adc.
=========================================

After updating windows 10 to 1 year anniversary edition
AND
updating LO to 5.2.0.4

I get a crash a startup when doubleclicking an odt file.
The file itself does not matter.
I think is has something to do with the docked windows: Style and Navigator.
When I remove both I can load the doc every time.
I then added the F11 Style sidebar, and also had no problems.
I then added the F5 Navigator.
The first time I started the odt it went ok.
The second time it crashed again.

I then get an Libreoffice Document Recovery window. However, it is not visible to the user, not in the taskbar, only in the taskmanager and the Alt-Tab icons! So a lot of users will miss this. If they then double-click on an odt now nothing will happen...

Also, "the following files will be recovered" list is empty.
I then get the crash report.
I then get to recover the file.
The Navigator and Style panels are showing.
If I exit and double-click the odt the same thing happens.

If I remove the Navigator, exit and double-click the odt it works ok
Comment 1 Aron Budea 2016-08-08 15:10:28 UTC
Closing as duplicate.

*** This bug has been marked as a duplicate of bug 100870 ***