Created attachment 130338 [details] Crash_print_screen Hi, I was testing one of my bugs on current "fresh" version and just to make sure the problem is not already fixed I downloaded LibreOffice master file: libo-master~2017-01-11_23.07.37_LibreOfficeDev_5.4.0.0.alpha0_Win_x86.msi and tried to install it on Windows 7 SP1. To my surprise LibreOffice crashed at start-up. How I installed: 1. Double click on exe file. 2. Everything in install dialogs I have left default and installed. How I started up LibreOffice: 1. On desktop icon was created I clicked on the icon and it took a while (probably Windows was recording the crash problem) and then "LibreOfficeDev has stopped working" dialog appears. I am not really an expert of debugging LibreOffice. Is there anything I can do to help diagnose this problem? Regards
I tried to locate the problem in previous master versions so I installed: libo-master~2016-12-28_23.10.06_LibreOfficeDev_5.4.0.0.alpha0_Win_x86.msi currently the oldest version from: http://dev-builds.libreoffice.org/daily/master/Win-x86@42/ and problem is already in this version, so crash at LibreOffice start-up. By the way I was trying to test the problem on 5.3-dev and on 5.2-dev but I see folders: http://dev-builds.libreoffice.org/daily/libreoffice-5-3/ and http://dev-builds.libreoffice.org/daily/libreoffice-5-2/ are empty, no Windows version to download. If I can help in anyway to diagnose this problem, please let me know and please point me to some documentation how to debug a problem.
It happened to me a few day ago but it seems to be fixed nowadays. Could you please try to test it with http://dev-builds.libreoffice.org/daily/master/ ? Regards
@Xisco, testing the master was my first test, see the "Description" of this bug. P.S. I am setting status back to UNCONFIRMED.
Yes, I know, but could you please use the link I put before?
@Xisco, I don't really understand... In "Description" (my first post) I have tested with: http://dev-builds.libreoffice.org/daily/master/Win-x86@42/2017-01-11_23.07.37/libo-master~2017-01-11_23.07.37_LibreOfficeDev_5.4.0.0.alpha0_Win_x86.msi Can you please point me to the "exe" file you would like me to test?
ok, Sorry for the noise. Actually you're testing the build I mentioned. For me, it crashed a few days ago but not anymore. I could, for instance, launch the safe mode. Could you try that? would resetting the profile fix your problem?
Hi, I have renamed C:\Users\igor\AppData\Roaming\LibreOffice\4 directory to C:\Users\igor\AppData\Roaming\LibreOffice\_4 so default profile directory does not exists any more. Running LibreOffice-master and it still crashes. But "LibreOfficeDev (Save Mode)" did start-up at least. Strange. What may be wrong? Is it something specific in my environment? Regards
(In reply to grofaty from comment #7) > Hi, > I have renamed C:\Users\igor\AppData\Roaming\LibreOffice\4 directory to > C:\Users\igor\AppData\Roaming\LibreOffice\_4 > so default profile directory does not exists any more. Running > LibreOffice-master and it still crashes. Shouldn't it be LibreOfficeDev\4, though? I can't think of anything else than OpenGL. Do you have such a log: C:\Users\User\AppData\Roaming\LibreOfficeDev\4\cache\opengl_device.log
Hi, all tests bellow on LibreOffice master on Windows 7 Professional Service Pack 1 (as virtual guest machine) inside VirtualBox 4.3.38 on Ubuntu 14.04 (as virtual host machine). TEST 1 1. Today I have downloaded fresh master from: http://dev-builds.libreoffice.org/daily/master/Win-x86@42/current/libo-master~2017-01-20_02.26.12_LibreOfficeDev_5.4.0.0.alpha0_Win_x86.msi and still crashing. 2. I have deleted C:\Users\igor\AppData\Roaming\LibreOfficeDev\4 folder so now only C:\Users\igor\AppData\Roaming\LibreOfficeDev folder exists with no subfolders. 3. I have double click "LibreOfficeDev 5.4" icon from desktop. 4. Then nothing happens for 20 seconds (I have measured with stopwatch) and then Windows crash window appears with the same dialogs as in my first post in this bug report. @Buovjaga you suspect this is OpenGL problem. I am attaching file C:\Users\igor\AppData\Roaming\LibreOfficeDev\4\cache\opengl_device.log. TEST 2 5. I clicked: Start | LibreOfficeDev (SaveMode) and LibreOffice starts-up and I selecting "Continue in Safe Mode" button and LibreOffice starts up successfully. TEST 3 6. Continue from TEST 2. Tools | Options | View | from Graphics Output I have unchecked all of the settings (hardware acceleration, anti-aliasing, OpenGL), so all of the settings in this section are unchecked and click on OK button. 7. Dialog pop-ups up to restart LibreOffice. I clicked on "Restart Now". 8. Safe Mode dialog pop-ups. I clicked on "Restart in Normal Mode". 9. After 20 seconds Windows crash dialog appears (the same as in step 4). Anything else I can test? Regards
Created attachment 130571 [details] Opengl_device.log
(In reply to grofaty from comment #9) > TEST 2 > 5. I clicked: Start | LibreOfficeDev (SaveMode) and LibreOffice starts-up > and I selecting "Continue in Safe Mode" button and LibreOffice starts up > successfully. This is the interesting bit. It works in Safe mode, but does not work with a clean profile. I don't really know enough about Safe mode to say, how this is possible. It's good to know you are using a virtual machine.
(In reply to grofaty from comment #9) > TEST 3 > 6. Continue from TEST 2. Tools | Options | View | from Graphics Output I > have unchecked all of the settings (hardware acceleration, anti-aliasing, > OpenGL), so all of the settings in this section are unchecked and click on > OK button. > 7. Dialog pop-ups up to restart LibreOffice. I clicked on "Restart Now". > 8. Safe Mode dialog pop-ups. I clicked on "Restart in Normal Mode". > 9. After 20 seconds Windows crash dialog appears (the same as in step 4). Got some advice from Samuel on IRC. First, you tried to change settings while in Safe mode: the settings will NOT be saved. Second, the only difference between normal mode + clean profile vs. Safe mode is: hardware acceleration is disabled in Safe mode. So it looks like hw accel might be the cause of the crash in your virtual machine. You should do this in the Safe mode dialog: Configure: Disable hardware acceleration. Apply changes and restart.
The same problem with crashes at start-up with: a) master~2017-01-23_03.24.17_LibreOfficeDev_5.4.0.0.alpha0_Win_x86.msi b) libreoffice-5-3~2017-01-22_22.43.21_LibreOfficeDev_5.3.1.0.0_Win_x86_en-US_de_ar_ja_ru_vec_qtz.msi @Buovjaga, I did as you suggested: 1. Start | LibreOfficeDev (SafeMode). 2. In opened "Safe Mode" dialog clicked on "Configure and checked "Disable hardware acceleartion (OpenGL, OpenCL)" and clicked on "Apply Changes and Restart". 3. LibreOffice starts up successfully. It looks like something got to be changed in LibreOffice 5.3+, because I have never experienced this crashes before and official LibreOffice Fresh 5.2.4.2 is working with "hardware acceleration" enabled.
grofaty: you could try this method: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#Automation Hopefully it would attach to the LibreOffice process before the crash happens You would have to use this debug build: http://dev-builds.libreoffice.org/daily/master/Win-x86@39/current/ ..and read from the beginning of the Windbg article, if you have never set it up.
Hi, sorry I have been real busy... Today after two mounts of last testing I have downloaded "LibreOffice master" on Windows 7. From Help | About Version: 5.4.0.0.alpha0+ Build ID: bdf41d8aeb53a298780f3633a76d71598a695bab CPU threads: 3; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-03-22_01:32:59 Locale: sl-SI (sl_SI); Calc: group 1. I selected "Custom" when installing and then left default. 2. I have executed created shortcut on desktop and LibreOffice starts without a problem. 3. I close down opened program. In Windows Explorer I have double clicked on swriter.exe to start LibreOffice Writer and it starts without a problem. I have also double clicked on scalc.exe and LibreOffice Calc starts up without a problem. It looks like in two moths period when I last tested something got to be changed in LibreOffice that fixed the problem. You can close down this report as not relevant anymore. Thanks for help.
Thank you for retesting. Closing as WFM.