Bug 98129 - Writer crashes all the time for no apparent reason
Summary: Writer crashes all the time for no apparent reason
Status: RESOLVED DUPLICATE of bug 97700
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: VCL-OpenGL
  Show dependency treegraph
 
Reported: 2016-02-24 09:35 UTC by Dirk Munk
Modified: 2016-02-26 11:27 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Munk 2016-02-24 09:35:59 UTC
I installed 5.1.0.3 (I came from 5.0.4), and started writing a new Writer document. Within seconds Writer crashed. I went on editing the document, but Writer kept on crashing all the time, even when I wasn't using it, or when I wasn't working with the laptop at all.

So I gave up and installed 5.0.5, no problems so far.
Comment 1 Buovjaga 2016-02-24 09:48:11 UTC
It is probably because of OpenGL being enabled due to a mistake in 5.1 release.

You can use this to safely try 5.1.1: https://wiki.documentfoundation.org/SI-GUI

Hopefully you still have this file after running 5.1.0:
C:\Users\User\AppData\Roaming\LibreOffice\4\cache\opengl_device.log

Would be cool to know what is in it.

Setting to NEEDINFO while we wait for your results.
Comment 2 Dirk Munk 2016-02-24 11:43:18 UTC
The log file isn't very interesting...

DriverVersion: 10.18.10.4276
DriverDate: 8-17-2015
DeviceID: PCI\VEN_8086&DEV_0166&SUBSYS_71021558&REV_09
AdapterVendorID: 0x8086
AdapterDeviceID: 0x0166
AdapterSubsysID: 0x71021558
DeviceKey: System\CurrentControlSet\Control\Video\{9F41D2F2-9AC4-4E1F-B314-5DEA806CDEDE}\0000
DeviceString: Intel(R) HD Graphics 4000
Comment 3 Buovjaga 2016-02-24 11:49:59 UTC
(In reply to Dirk Munk from comment #2)
> The log file isn't very interesting...

Sure it is :)

Let me know, if 5.1.1 fixes the issue.
Comment 4 Michael Meeks 2016-02-24 13:28:19 UTC
Can you get a stack trace from the crash ?

https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

you seem to have a reasonably new driver - which is good =)

Thanks !
Comment 5 Dirk Munk 2016-02-24 15:24:34 UTC
5.1.1. is working perfectly, no problems what so ever. During the installation I had to close two browsers because a component was updated that was also in use by the browsers. Interesting .......

I noticed that the 5.0.5. deinstall procedure also worked fine, with 5.0.4. I had the old problem that the program directory in the libreoffice directory was left in a state of ?!?!, You couldn't use it or delete it, and you had to reboot. After the reboot the directory was gone.
Comment 6 Buovjaga 2016-02-25 14:21:46 UTC
(In reply to Dirk Munk from comment #5)
> 5.1.1. is working perfectly, no problems what so ever. During the
> installation I had to close two browsers because a component was updated
> that was also in use by the browsers. Interesting .......
> 
> I noticed that the 5.0.5. deinstall procedure also worked fine, with 5.0.4.
> I had the old problem that the program directory in the libreoffice
> directory was left in a state of ?!?!, You couldn't use it or delete it, and
> you had to reboot. After the reboot the directory was gone.

Can you get it to crash in 5.1.1, if you enable: Tools - Options - LibO - View - Use OpenGL for all rendering AND Force OpenGL? The setting might get disabled automatically after a crash.

If you can get it to crash in 5.1.1, Michael might be interested in a backtrace like he said.
Comment 7 Dirk Munk 2016-02-25 22:25:18 UTC
OpenGL was enabled, so 5.1.1. is behaving perfectly. No crashes!
Comment 8 Buovjaga 2016-02-26 09:10:42 UTC
All right, it seems some major bug was fixed then :) Setting to WFM as we don't know the commit.
Comment 9 Michael Meeks 2016-02-26 11:27:56 UTC
Phew; that is encouraging - I suspect it was the DMA texture memory corruption issue that we  fixed here.

Thanks for the report & for re-testing 5.1.1 ! =)

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