Bug 115628 - Crash on closing extension manager after check for update
Summary: Crash on closing extension manager after check for update
Status: RESOLVED DUPLICATE of bug 115420
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.1.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: VCL-OpenGL
  Show dependency treegraph
 
Reported: 2018-02-11 11:54 UTC by StamatisZ
Modified: 2018-02-12 21:45 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
opengl_device.log Nvidia GTX970 (314 bytes, text/plain)
2018-02-12 21:45 UTC, StamatisZ
Details

Note You need to log in before you can comment on or make changes to this bug.
Description StamatisZ 2018-02-11 11:54:30 UTC
Description:
On closing the exetnsion manager after having checked for updates crashes Libreoffice

Steps to Reproduce:
Prerequisites:
- installed extension: LanguageTool v4.0
- Java 1.8.0.161
1. Start Libreoffice (no open Documents)
2. Open Extension Manager
3. Check for Updates (no Updates found)
4. Close Extension Manager
-> Libreoffice crashes and produces crash report

Actual Results:  
Crash

Expected Results:
No Crash


Reproducible: Always


User Profile Reset: No



Additional Info:
crashreport.libreoffice.org/stats/crash_details/9cfd899d-8027-4ed2-b91b-bdc74c126d38

Version: 6.0.1.1 (x64)
Build-ID: 60bfb1526849283ce2491346ed2aa51c465abfe6
CPU-Threads: 12; BS: Windows 6.1; UI-Render: GL; 
Gebietsschema: de-DE (de_DE); Calc: group


User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Comment 1 V Stuart Foote 2018-02-11 19:08:58 UTC
Confirmed on Windows 10 Home 64-bit en-US with
Version: 6.0.1.1 (x64)
Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
Locale: en-US (en_US); Calc: CL

crashreport.libreoffice.org/stats/crash_details/062bc72f-7c94-4d55-818e-352ab3369c2c

With OpenGL enabled, just opening the Extension Manager -> Check for Updates -> Close -> Close: Crash and recover on relaunch

And, what happens if you disable Tools -> Options -> View: "Use OpenGL for all rendering"?

For me, no crash.
Comment 2 Roman Kuznetsov 2018-02-11 19:53:27 UTC
Confirmed on Windows 7 64 bit

Version: 6.0.1.1 (x64)
Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6
CPU threads: 4; OS: Windows 6.1; UI render: GL; 
Locale: ru-RU (ru_RU); Calc: CL

JRE 1.8.0.66
LanguageTool is not installed!

Without OpenGL -> no crash
Comment 3 V Stuart Foote 2018-02-11 20:12:27 UTC
Crash on master with same STR of opening Extension manager with OpenGL rendering enabled -> Check for Updates -> Closing the check for updates will crash.

Just have to load at least one .OXT extension for the check for updates to be enabled. 

Version: 6.1.0.0.alpha0+ (x64)
Build ID: 609888f3c8d6c0fe72c41ac26de431a12ad3fdd0
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-02-08_02:03:29
Locale: en-US (en_US); Calc: CL
Comment 4 Julien Nabet 2018-02-11 20:12:49 UTC
Given the crashreport, it seems a dup.

Could you attach <user profile>/cache/opengl_device.log? (see https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28OpenGL.29)

*** This bug has been marked as a duplicate of bug 115420 ***
Comment 5 StamatisZ 2018-02-12 21:45:28 UTC
Created attachment 139844 [details]
opengl_device.log Nvidia GTX970

opengl_device.log as requested