Description: LibreOffice crashes when selecting a (Visio?) drawing Steps to Reproduce: 1.Open attached file 2.Select the vertical 'table' on the first page Actual Results: Crash Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info: Found in: Version: 5.4.0.0.alpha0+ Build ID: 9cfb2f2f03b5ec086487fd483298466db0b09010 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-20_23:58:02 Locale: nl-NL (nl_NL); Calc: CL and in Versie: 4.4.6.3 Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d Locale: nl_NL User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Created attachment 129844 [details] Example file
On pc Debian x86-64 with master sources updated today, I don't reproduce this with gtk3, gtk, kde4 or gen rendering but when opening the file, I noticed these logs: warn:legacy.tools:22030:1:svx/source/svdraw/svdoole2.cxx:1335: The destination model must have a persistence! Please submit an issue! warn:legacy.tools:22030:1:svx/source/svdraw/svdoole2.cxx:1336: The source and the destination models should have different persistences! Problems are possible!
Created attachment 129853 [details] bt with symbols from console log
I can't reproduce it in Version: 5.4.0.0.alpha0+ Build ID: 5a20df55ff829978c880b22e0a1f32c35d0ba30f CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group nor Version: 5.4.0.0.alpha0+ Build ID: 53edf60c4ce6ed32f87471e018878c40b788005a CPU Threads: 1; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-18_06:57:59 Locale: es-ES (es_ES); Calc: group However, I see that in Windows there's no right border...
Sounds like system specific, or it's caused by Visio 2016 trail version.
No crash. Telesto: if you can get it to crash with a TB39 build, you could get a backtrace with WinDbg. Win 10 Version: 5.4.0.0.alpha0+ Build ID: 7ed40deee74a9869b7da073ad473241187420ff8 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-30_23:18:54 Locale: fi-FI (fi_FI); Calc: group
Created attachment 130068 [details] WinDBG Backtrace Version: 5.4.0.0.alpha0+ Build ID: 7a1add76d542e9929c1feab9e06949990e236616 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-12-22_23:56:14 Locale: nl-NL (nl_NL); Calc: CL
Thank you Telesto for the bt. I noticed this method OleComponent::GetVerbList on your bt (see http://opengrok.libreoffice.org/xref/core/embeddedobj/source/msole/olecomponent.cxx#1012) so could be Windows only bug. I'm not sure but it seems m_pNativeImpl->m_pOleObject could be not initialized. Indeed, we don't call InitializeObject_Impl method which initializes it. If this is the case, either we should explicitely call it or we should call a method which itself calls it (hope it's clear enough :-)) Do you build yourself from sources? If yes you may add some debug traces in this method to know precisely where it crashed. Anyway, let's put this one to NEW since there's a bt. Mike: I don't know any official OLE expert in LO. But noticing this commit https://cgit.freedesktop.org/libreoffice/core/commit/?id=5ecd7ebbdf752eac48442006137d62426bf63c84 thought you might be interested in this one.
*** Bug 108114 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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
it doesn't crash in Versión: 6.2.4.2 Id. de compilación: 2412653d852ce75f65fbfa83fb7e7b669a126d64 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 @Telesto, could you please try again in master ?
oh wait, i don't have Visio installed...
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 https://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
What do you mean by "selecting"? Just select the object using a single click? For me LO 7.6 dev master didn't crash. Also, by double clicking on the object I can edit that in LibreOffice Draw without problem. Not reproducible with LO 7.6 dev master: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 52f70f04bdc586a072141e069d451a979c5f4cb7 CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_DE); UI: en-US Calc: CL threaded I also don't have Visio installed.