Created attachment 134501 [details] Example file This bug was filed from the crash reporting server and is br-81e4820d-8e70-44d5-9677-760191d76ff0. ========================================= 1. Extract the attached file 2. Open the demo file 3. Stress LibreOffice by entering and exiting the Ole-object 3a. Double click the ole object 3b. Deselect the ole object 3c. Enter the object again (double click) 3d. Repeat step 3a-3c It will crash at some point
I can confirm with Version: 6.0.0.0.alpha0+ (x64) Build ID: 7b4f4f15971047664fa278fff96b959d53b272b3 CPU threads: 1; OS: Windows 6.1; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-07-08_01:39:24 and 4.2.8
I can't reproduce it in Version: 6.2.0.0.alpha0+ Build ID: d60d695fcc5064e1f16842387fdce23456a64694 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: x11; Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded nor in Versión: 6.0.4.2 Id. de compilación: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group @Telesto, @raal, How many times do you have to repeat steps 3a-3c?
Repro with Version: 6.2.0.0.alpha0+ Build ID: 51aa57cd8ed46d28262e0d315328231f0fa814f4 CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-12_05:54:56 Locale: nl-NL (nl_NL); Calc: CL 1. Extract the attached file 2. Open the demo file 3. Double Click the blue OLE object 4. Click outside the OLE object (while it's still opening) 5. Macro dialog appears (press OK) 6. Double click the OLE object again -> crash
Still repro : 3a. Double click the ole object 3b. Deselect the ole object 3c. Enter the object again (double click) confirm macro warning Deselect the ole object Double click the ole object Crash Version: 6.2.0.0.alpha0+ (x64) Build ID: c3e552ac25be001a623469c549ee8d0719b98133 CPU threads: 1; OS: Windows 6.1; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-06-14_00:15:12
Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still reproducible in Version: 6.4.0.0.alpha0+ Build ID: af37bb23f63b209af1193e20177c3aacbd777543 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
Just for the record, I reproduce it one time out of 10, maybe be a race condition
Created attachment 177141 [details] Backtrace
Created attachment 189332 [details] bt with debug symbols On pc Debian x86-64 with master sources updated today, I got an assertion.
Julien Nabet committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/4a501a7270a0dd476ff71f72fae2c9fb9b40520a Related tdf#108976: Crash in: OutputDevice::GetOutputSizePixel() It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
The patch I submitted is just related and concerned an assertion not a crash. Could someone give a new try with a recent LO version? (eg: 7.5.5)
No repro with: Version: 7.6.5.0.0+ (X86_64) / LibreOffice Community Build ID: 13c748e7998b6df02e23815f337e9ab4d04172f3 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded I did not even get a macro pop-up warning.