Created attachment 113910 [details]
This is the file that caused the crash. Pretty simple indeed; 13 tabs and some data validation rules.
I found a Major misbehavior in LibreOffice 4.4.x,
when I try to open an .xls file (created with MS Excel), which I always was able to manage and modify using earlier versions of LibreOffice, the program crashes triggering the file recovery procedure.
The file recovery procedure also hangs, entering in an infinite loop in which I can only choose to discard the recovered file to get out.
I'm attaching the file that produced this behavior.
No crash with 184.108.40.206, win7. I can open file without problem.
No crash with Version: 220.127.116.11.alpha0+
Build ID: a2fa9e2468aa5c4fd4b610c5d0ebc8959e87a072
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-02-23_02:34:05
Please test with LO 18.104.22.168
I can confirm (I just tested it) that version 4.3 can open the file without problems.
So sorry, I added my previous comment without noticing the request!
I also tested with the latest stable version, 4.4.1, on a Windows 7 32bit - and it still crashes.
So I had to rollback to the 22.214.171.124 version, that works for me
Ubuntu 14.10 x64
LibreOffice 126.96.36.199 release
Opens with no problems. Please try with a fresh profile: https://wiki.documentfoundation.org/UserProfile
no crash under Win8x64 using LibO 188.8.131.52
please reset user profile like Joel suggested and tell if it fixes things.
set status to NEEDINFO waiting for feedback
I reset the user profile adding the -OLD suffix to the "user" folder found in C:\Users\MYUSERNAME\AppData\Roaming\LibreOffice\4 ,
but the issue still isn't fixed.
I have LO version 184.108.40.206, on Windows 7 32 bit
If possible, please follow the instructions provided at this link < https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg > and submit a backtrace. That way a developer can look into the underlying reason of the crash.
Summary -> (hard to repro)
Adding to the "no repro" pile.
Win 7 Pro 64-bit, Version: 220.127.116.11
Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6
Build ID: 8c3cf9dd48e40604867d3a28bddaccd65142df17
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-03-27_15:15:18
(In reply to raal from comment #7)
> If possible, please follow the instructions provided at this link <
> https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg > and
> submit a backtrace. That way a developer can look into the underlying reason
> of the crash.
I (maybe) have finally managed to get a backtrace: I'm attaching the .txt
Hope this helps
Created attachment 114695 [details]
The backtrace of the action that causes the application crash
Linked bug 90483 which also seems related to OpenCL and "amdocl"
Adding Cc: to email@example.com - moggi suggested I ping you about this one. Taken together with bug 90483, it's possible an OpenCL blacklist entry may be needed
Alessandro - this is most interesting; is there any chance of getting some information about your OpenCL setup ?
Either the output of running 'clinfo.exe' on the windows console; or going to:
and getting a screenshot of that; I guess it'd be interesting to switch to another CL implementation to see if that affects things. Needless to say it works fine for my OpenCL / Linux machine so we may need to tweak white/black lists here.
Created attachment 115337 [details]
OpenCL info screenshot
I've added the screenshot you required (the clinfo.exe command crashed every time i tried to run it...)
Hope it helps!
> I've added the screenshot you required (the clinfo.exe command
> crashed every time i tried to run it...)
If the most simple 'clinfo.exe' command crashes on run; then (somehow) you have mis-configured your system horribly, and the OpenCL stack is broken - which is outside of LibreOffice's control ? Can you try fiddling with that, to the point that clinfo.exe works again ? =)
Beyond that, your screen is rather odd I guess. No idea why the string "Linux" appears in that dialog on Windows =)
well I have no clue as of how the system has been setup (it is my office desk PC)
but I will try and investigate the matter.
Happy it's not Libreoffice's fault, I'm trying to fiddle a bit and update you in case I find something new
Thank you for your great work, guys!
Not reproduced on Windows 7 64-bit with the same "OpenCL info screenshot".
I'll close this one, but feel free to reopen with some new info.
Please update the computer and solved the clinfo before.