Bug 105029 - Crash in: vm3dgl.dll EDITING
Summary: Crash in: vm3dgl.dll EDITING
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
5.2.4.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks:
 
Reported: 2017-01-01 12:59 UTC by Dag Bjerkeli
Modified: 2017-12-14 11:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["vm3dgl.dll"]


Attachments
ZIP-file with two drawings opened during crash. (30.62 KB, application/zip)
2017-01-01 12:59 UTC, Dag Bjerkeli
Details
Menues does not display correctly (115.97 KB, image/png)
2017-01-01 23:30 UTC, Dag Bjerkeli
Details
Garbled drawing (29.04 KB, image/png)
2017-01-01 23:32 UTC, Dag Bjerkeli
Details
VMware workstation crash while testing LO (27.78 KB, image/png)
2017-01-01 23:33 UTC, Dag Bjerkeli
Details
opengl_device.log (301 bytes, text/x-log)
2017-01-02 00:45 UTC, Dag Bjerkeli
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dag Bjerkeli 2017-01-01 12:59:48 UTC
Created attachment 130072 [details]
ZIP-file with two drawings opened during crash.

This bug was filed from the crash reporting server and is br-20bd5a80-ad68-4b63-9868-22016156ab54.
=========================================

This crash came when I wanted to investigate some serious slowness editing drawings in Ubuntu, so I installed Libre Office in a virtual Windows machine. Opening two drawings (attached) and clicket one element in one of the drawing and LO crashed.

Starting LO and reopening those drawings did not crash program again.
Comment 1 Julien Nabet 2017-01-01 18:52:23 UTC
Would it be possible you apply advice from https://wiki.documentfoundation.org/QA/FirstSteps ? (in peculiar OpenGL part)
Comment 2 Dag Bjerkeli 2017-01-01 19:37:19 UTC
Thanks for prompt reply and happy new year!

Starting LO showed Standard Render. Setting render to OpenGL and restarting LO gave me weird behaviour in the program, but no crash.

I removed the user profile, and I got a behaviour similar to when I had the crash. Help->About box was black, but managed to see the text by highlighting the text and then it reviled that render was OpenGL.

Could it be that the crash sat the render to standard?
Comment 3 Julien Nabet 2017-01-01 22:09:07 UTC
(In reply to Dag Bjerkeli from comment #2)
> Thanks for prompt reply and happy new year!
> 
> Starting LO showed Standard Render. Setting render to OpenGL and restarting
> LO gave me weird behaviour in the program, but no crash.
> 
> I removed the user profile, and I got a behaviour similar to when I had the
> crash. Help->About box was black, but managed to see the text by
> highlighting the text and then it reviled that render was OpenGL.
> 
> Could it be that the crash sat the render to standard?

I'm not sure to have understood, do you reproduce the crash with OpenGL disabled or enabled?
If reproduced with OpenGL enabled, "locate <user profile>/cache/opengl_device.log, and attach it to the bug report" as the link quoted in my previous comment indicates.
If reproduced with OpenGL disabled, I must recognize I don't know what to think then since your bt clearly shows methods related to OpenGL.
Comment 4 Dag Bjerkeli 2017-01-01 23:30:51 UTC
Created attachment 130077 [details]
Menues does not display correctly
Comment 5 Dag Bjerkeli 2017-01-01 23:31:40 UTC
I did not manage to reproduce the crash. Turning OpenGL on gave weird behaviour. Deleting the user profile likewise.

With weird behaviour I mean black dialogue boxes, menu lists black and garbled drawing.

Upon opening more drawings (3 open at same time) the VM crashed.
I'm attaching opengl_device.log, screenshots of drawing problem and workstation crash dialogue.
Comment 6 Dag Bjerkeli 2017-01-01 23:32:25 UTC
Created attachment 130078 [details]
Garbled drawing
Comment 7 Dag Bjerkeli 2017-01-01 23:33:37 UTC
Created attachment 130079 [details]
VMware workstation crash while testing LO
Comment 8 Dag Bjerkeli 2017-01-02 00:45:00 UTC
Created attachment 130080 [details]
opengl_device.log
Comment 9 Julien Nabet 2017-01-02 10:22:47 UTC
Thank you for all these information.
Since I got no more questions, I'll put it to NEW since there's a bt.
Comment 10 Xisco Faulí 2017-12-14 11:42:16 UTC
Taking into account this issue was put into NEW without steps to reproduce it and the crash signature hasn't been reported for 5.4.* or 5.3.7, I'm closing this as RESOLVED WORKSFORME.
Feel free to open it again if the issue is reproduced again on the latest version of LibreOffice