Bug 106264 - Writer crashes on startup in: cppu::_copyConstructAnyFromData(_uno_Any *,void *,_typelib_TypeDescriptionReference *,_typelib_TypeDescription *,void (*)(void *),_uno_Mapping *)
Summary: Writer crashes on startup in: cppu::_copyConstructAnyFromData(_uno_Any *,void...
Status: VERIFIED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-01 22:10 UTC by larsie13
Modified: 2017-03-29 11:31 UTC (History)
3 users (show)

See Also:
Crash report or crash signature: ["cppu::_copyConstructAnyFromData(_uno_Any *,void *,_typelib_TypeDescriptionReference *,_typelib_TypeDescription *,void (*)(void *),_uno_Mapping *)"]

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description larsie13 2017-03-01 22:10:15 UTC 
This bug was filed from the crash reporting server and is br-29c807c5-48c8-4039-a8b7-49732c89e457.
=========================================
Long story short: Writer crashes on startup. LO then asks to submit a crash report, followed by the document recovery dialog. Then it automatically starts Writer again (instead of opening the main dialog showing recent documents), which promptly crashes again. The only way out of this loop is by terminating the LO process and opening it back up by starting something other than Writer or Draw (Draw is also affected by the same problem, but Calc and Impress are not). 

I've first started seeing this bug yesterday, when I was still on 5.1.5. Updating to 5.3.0.3 did not fix it.

I realize that although I can this perfectly reproduce it every time by simply opening Writer or Draw (either with a new document or an existing one), it is probably not easy to reproduce for others (since it is likely specific to certain OS configurations). Nonetheless, while this bug stands, it is impossible for me to use Writer or Draw.
Comment 1 Xisco Faulí 2017-03-01 22:39:06 UTC Comment hidden (obsolete)
Comment 2 larsie13 2017-03-01 22:49:55 UTC 
I forgot to mention that I already tested it in safe mode. The results were the same.
But just to be safe, I just tested it in safe mode again; still the same.
Comment 3 Xisco Faulí 2017-03-01 22:58:37 UTC 
Does disabling OpenCL from safe mode help to improve the situation?
Comment 4 larsie13 2017-03-01 23:08:28 UTC 
Nope, no change. I thought I might as well see if Java had anything to do with it, however unlikely, but disabling that did not change anything, either.
Comment 5 Buovjaga 2017-03-04 18:38:18 UTC 
(In reply to Xisco Faulí from comment #3)
> Does disabling OpenCL from safe mode help to improve the situation?

Note, this should say "OpenGL" and not "OpenCL".
Comment 6 larsie13 2017-03-04 21:54:11 UTC 
Disabling OpenGL, too, changes nothing.
Comment 7 larsie13 2017-03-05 20:35:23 UTC 
I don't know if I should mention this here, but the same also happens in Calc as soon as I press F11 to display the Styles sidebar. Crash report ID: d6d6f6e3-3a0e-4e77-ac72-4a842d407a01
Comment 8 Buovjaga 2017-03-06 06:52:25 UTC 
Just to check, you can try this fresh build: http://dev-builds.libreoffice.org/daily/master/Win-x86@42/current/
It will not overwrite your 5.3, but will install alongside it.
Comment 9 larsie13 2017-03-06 17:08:45 UTC 
I wasn't expecting much, but it actually works fine in the dev build.
Could it be something that is already fixed in the dev build?
The only other things I can think of are related to my user profile, which would mean it should not happen in safe mode.
Comment 10 larsie13 2017-03-06 17:09:33 UTC 
To clarify: when I say "it works fine", I'm referring to Writer, Draw AND Calc.
Comment 11 Buovjaga 2017-03-07 06:49:15 UTC 
Yes, it is weird as it can't be about your user profile. Maybe there was some bug specific to your system and it is fixed after 5.3.

You can choose to leave this open or close as RESOLVED WORKSFORME.
Comment 12 larsie13 2017-03-08 18:53:26 UTC 
I'd like to leave it open for now.
Then once 5.4 is officially released, I'll see if updating my regular installation to 5.4 also fixes it.
Comment 13 Xisco Faulí 2017-03-08 21:17:53 UTC 
(In reply to larsie13 from comment #12)
> I'd like to leave it open for now.
> Then once 5.4 is officially released, I'll see if updating my regular
> installation to 5.4 also fixes it.

The procedure in this kind of situations is to close it as RESOLVED WORKSFORME and add the whiteboard backportRequest to see if someone can bisect it and identify the commit that fixed it.
You can find more information about the bisect concept in: https://wiki.documentfoundation.org/QA/Bibisect
Comment 14 larsie13 2017-03-28 20:44:12 UTC 
I just updated to 5.3.1.2 and I can confirm that it is also fixed there.
Comment 15 Aron Budea 2017-03-29 11:31:30 UTC 
Great, thanks for the verification.