Problem description: Files with .ods extension that are not actually .ods files crash Windows Explorer Steps to reproduce: 1. Create a tab-delimited .txt file 2. Rename it to .ods 3. Visit its folder and select the file or set folder for thumbnail view Current behavior: Windows Explorer crashes Expected behavior: Ignore invalid files Platform (if different from the browser): Windows 7 Pro SP 1 64-bit Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1
At least I can say that short after installation of 3.6 I also had lots of WIN Explorer Crashes with WIN7 64 bit. But I did not find the reason, and currently I can not test because I do not have installed 3.6. @Reporter: Does the problem persist when you Change Installation and install newly without WIN EXPLORER Extension?
Correct, the problem goes away if I use the installer, Modify, and disable the Windows Explorer Extension. If I re-enable the extension and click on the file, it crashes.
I can not reproduce that problem with a very simple 2 Rows 3 Columns "csv.ods" (creeated due to report) and parallel installation of Master "LOdev 3.7.0.0.alpha0+ - ENGLISH UI / German Locale [Build ID: c7e559]" {tinderbox: @16, pull time 2012-10-03 05:46:26} on German WIN7 Home Premium (64bit). Only particular Version related? Something else? I will test 3.6.1.2. during weekend. for a while I had so many crashes, that I doubt that invalid.ods is the only reason what might cause crashes. @Reporter: Please attach such a document what reliably crashed the explorer. From what Version did you update to 3.6.1.2? Any Idea what particular settings or what ever else might be involved?
Hm, may be it is some more easy and this one simply is a DUP of "Bug 53533 - shlxthdl_x64.dll/shlxthdl.dll causes Windows Explorer to CRASH when corrupted ODF file is in view"? @7qia0tp02: Can you please test 3.6.2 before we do further debug efforts?
No further feedback from bug reporter. Could you please try using LO 4 and see if this issue persists? In that case please re-open this bug and we'll further investigate how to tackle this problem.
Due to details I am sure that this one is a DUP as supposed in Comment 4. @reporter: Please feel free to reopen this Bug if you find evidence that we have an independent issue here (for example because the fix for the other bug does not work for you). *** This bug has been marked as a duplicate of bug 53533 ***