Title says all. Open math, create a formula, export to pdf, boom it crashes. I've clicked to send reports to LO.
Confirmed on windows 7 x64 with Version: 6.2.6.2 (x64) Build ID: 684e730861356e74889dfe6dbddd3562aae2e6ad CPU threads: 3; OS: Windows 6.1; UI render: default; VCL: win crashreport.libreoffice.org/stats/crash_details/5e15b89f-4b81-4e44-b81f-fa98b7491ebc
Happened on my PC with Win8.1 Pro(64bit)
Can not confirm on Windows 10 Home 64-bit en-US (1903) with Version: 6.4.0.0.alpha0+ (x64) Build ID: 3e64065612acec2eb29aa21e2b515953422256d7 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-08-15_22:57:26 Locale: en-US (en_US); UI-Language: en-US Calc: threaded Export to PDF from sm Formula editor creates readable PDF.
(In reply to V Stuart Foote from comment #3) > Can not confirm on Windows 10 Home 64-bit en-US (1903) with > Version: 6.4.0.0.alpha0+ (x64) > Build ID: 3e64065612acec2eb29aa21e2b515953422256d7 > CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; > TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-08-15_22:57:26 > Locale: en-US (en_US); UI-Language: en-US > Calc: threaded > > Export to PDF from sm Formula editor creates readable PDF. This build also WFM with Default rendering, not OpenG
Vincent/MM: In the crash report, I noticed LocaleData2, which locale do you use? (any better if you use EnglishUS?)
enUS. crashreport.libreoffice.org/stats/crash_details/5c42e43d-6194-4180-a33e-255f456ae8ce
Thank you Vincent for your feedback. Could someone attach an example file? (perhaps it's related to what operator is used in the formula) Indeed, with LO master sources updated today with Win10 I don't reproduce this.
For me, I simply did: 1) open Math 2) type: a = sin (1) 3) export as pdf 4) select a save file, ok. 5) Crash
Thank you MM for your feedback. I gave a try with master sources updated today + LO 6.3.0, I don't reproduce this. I'll give a try on my Linux machine.
Just updated to Version: 6.3.1.1 (x64) Build ID: e979878b49a48dab15ebe528f238b88125e32c65 CPU threads: 3; OS: Windows 6.1; UI render: default; VCL: win It crashes even in safe mode. With 6.2.6.2 it says it crash at: cppu::WeakComponentImplHelperBase::release() Now, with 6.3.1.1 it says it crashes at: std::char_traits<char>::copy(char * const,char const * const,unsigned __int64) http://crashreport.libreoffice.org/stats/crash_details/117b9a38-78ed-486e-a436-34c2cceed802
What options do you use for PDF export? Indeed, I gave a try with master sources updated today with gtk3 and gen rendering, no crash.
(In reply to Julien Nabet from comment #11) > What options do you use for PDF export? > Indeed, I gave a try with master sources updated today with gtk3 and gen > rendering, no crash. Just default options.
Can't reproduce it in Versión: 6.3.0.3 (x86) Id. de compilación: c75130c129d9c5e43b76e4f26881b3db8bdb5c91 Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Idioma de IU: es-ES Calc: threaded nor in Version: 6.4.0.0.alpha0+ Build ID: 41cd3e8e817c8c33a13608e62eeb06ce2c6977e4 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
Nor in Version: 6.4.0.0.alpha0+ (x64) Build ID: 744f70386727c78a19bd7c1de7425392b98783c7 CPU threads: 16; OS: Windows 6.3; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-US Calc: threaded
I can't reproduce it with Version: 6.4.0.0.alpha0+ (x64) Build ID: 01837a85004a6f891a09c0a63ed7eff75d634827 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-01_00:07:05 Locale: en-GB (de_DE); UI-Language: en-US Calc: threaded
Hello MM, VincentYu, Could you please try to submit a backtrace as described here https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg ?
No can't do. Don't have extra machine for development/testing. Sorry. You may close the bug now.
VincenYu, which version of Windows 10 do you use? We had similar bugs, where the problem disappearde after an upgrade from Windows 10 1809 to Windows 10 1903.
Summary of the crash reports indicates crashes from when it was created in LO 5.2 until LO 6.3. Question which is reporter's OS already answered in Comment 2: Windows 8.1. And MM confirmed with Win7 with LO 6.2. That being said, I don't repro steps from Comment 8 with LO 6.2 in Win7. MM, please try to turn off/on OpenCL and OpenGL in Tools-Options.
Summary of the crash reports indicates crashes from when it was created in LO 5.2 until LO 6.3. Question which is reporter's OS already answered in Comment 2: Windows 8.1. And MM confirmed with Win7 with LO 6.2. That being said, I don't repro steps from Comment 8 with LO 6.2 in Win7. Reporter and MM, please try to turn off/on OpenCL and OpenGL in Tools-Options. And also various in Tools > Options > Math > Settings > Print Options
Tried turn on/off OpenCL, same crash scenario.
one more crash report for 6.2.8.2
Version must correspond to the earliest one.
Unconfirmed on windows 10 x64 with Version: 6.3.4.2 (x64) Build ID: 60da17e045e08f1793c57c00ba83cdfce946d0aa CPU threads: 12; OS: Windows 10.0; UI render: default; VCL: win Unconfirmed on mint 19.3 x64 with Version: 6.5.0.0.alpha0+ Build ID: f6cf80c81043d84606a5b5f7d93ae958307a16d3 CPU threads: 5; OS: Linux 5.0; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-12-22_08:24:32 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded So it seems fixed.
Reproduced on newly installed 6.3.5.2 crashreport.libreoffice.org/stats/crash_details/f60c7bd0-d725-4d19-a604-b2c076ee13eb Version: 6.3.5.2 (x64) Build ID: dd0751754f11728f69b42ee2af66670068624673 CPU threads: 2; OS: Windows 6.3; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded
reproduced in 6.4.5.2 Version: 6.4.5.2 (x64) Build ID: a726b36747cf2001e06b58ad5db1aa3a9a1872d6 CPU threads: 2; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded The crash log has been submitted.
Vincent: don't remove version value since MM confirmed this with 6.2.6 (see comment 1) and version field must correspond to the earliest known LO version where we can encounter the bug.
Argh, just taken a new look and MM hadn't reproduced this on more recent LO version. So I understand now why you put undefined. Could you attach a new crashlog since it could be another cause?
Dear VincentYu, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear VincentYu, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp