Open ods file and LibreOffice crash

[pcplayer]

system: Windows 7 64bit.
I have try 6.1.2 and 6.0.6 WindowsX86_64 version. Uninstall, re-install, delete userprofile, enable OpenCL in libreOffice option, or disable it, etc. And then I open LibreOffice calc, input some number in three or four cells, save it as a test.ods. And when I open this test.ods file, LibreOffice crashs. Everytime I open any ods file it will crash.

I can open writer file normally.

And when I check Windows event info, below is the info:

---

错误应用程序名称: soffice.bin，版本: 6.1.2.1，时间戳: 0x5ba3a201
错误模块名称: HPM1210FPSU.DLL，版本: 0.3.1.58769，时间戳: 0x50668cf5
异常代码: 0xc0000409
错误偏移量: 0x0000000000046343
错误进程 ID: 0x27ec
错误应用程序启动时间: 0x01d4635e43d7cb8d
错误应用程序路径: C:\Program Files\LibreOffice\program\soffice.bin
错误模块路径: C:\Windows\system32\spool\DRIVERS\x64\3\HPM1210FPSU.DLL
报告 ID: 89843ed2-cf51-11e8-b037-8e03b04ec16d

---

So, it seems that the problem is caused by my HP printer driver.

Then I uninstall it. And then download Windows X86 version of LibreOffice V.6.1.2 and re-install. Problem has gone.

So, it seems that LibreOffice 64bit version conflict with HP printer driver – the newest version driver because after I re-install my HP printer driver my LibreOffice changed to unstable.

[Kruno]

Think that before closing such question user should be pointed to Bugzilla so user can upload spreadsheet that’s crashing LibreOffice there and provide information which he did here, but in English (change user interface to English first).

[mikekaganski]

@pcplayer: In this case, first please send a crash report. Then proceed to the link that the crash reported has given you, and there choose to create a bug report for Calc. In the bug report, you should keep the automatically added information about the crash, and describe the problem, mention OS and LO versions (taking into account what @Kruno said), printer model and driver version. attach the file that gives the problem (just in case someone has).

[mikekaganski]

It’s possible that you also will need to create a backtrace to help us to identify the problem, because it’s likely that the problem is caused by a specific software+hardware configuration that developers could not have. Please see https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg.