Description: When I switch from LibreOffice 32 bits to 64 bits version (I'm now on LibreOffice 6.0.4), and I open Writer, the program crashes and sends me to the Safe Mode. I have seen sometimes the crash reporter screen also. Steps to Reproduce: 1.Uninstall any version of LibreOffice 32 bits 2.Install any version of LibreOffice 64 bits 3.Start Writer Actual Results: It should work all flawlessly Expected Results: It crashes continuously Reproducible: Sometimes User Profile Reset: Yes Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Does it work if you disable OpenGl ? -> https://wiki.documentfoundation.org/OpenGL I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
No. I have always OpenGL disabled in Libreoffice. I will change the status to "UNCONFIRMED", because I can reproduce the issue sometimes. Also, I attach the string of the version. Versión: 6.0.4.2 (x64) Id. de compilación: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf Subprocs. CPU: 4; SO: Windows 10.0; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: CL Does OpenCL have influence on the crashes? If so, I could disable it, because, by default, is enabled always.
Seeing you're using Win 10, Is the OS updated? I recall reading some crashes which were fixed by applying the latest updates from Win 10
Yes, I'm using Windows 10 Fall Creators Update (1709). I use the OS compilation 16299.431. Does April Update solve this crashes?
(In reply to impreza233 from comment #4) > Yes, I'm using Windows 10 Fall Creators Update (1709). I use the OS > compilation 16299.431. Does April Update solve this crashes? Only you can answer that :)
(In reply to Buovjaga from comment #5) > (In reply to impreza233 from comment #4) > > Yes, I'm using Windows 10 Fall Creators Update (1709). I use the OS > > compilation 16299.431. Does April Update solve this crashes? > > Only you can answer that :) Yes. With April Update, compilation 17134.112, the problem is solved. Furthermore, I think that it could not be able to reproduce this problem on that Windows 10 version (and in Insider versions).