Description: On pc Debian x86-64 with master sources updated today, I got a crash in report editing. Steps to Reproduce: 1. Create a brand new hsqldb 2. Create a table with wizard 3. Create a new report with editor (not wizard) 4. Insert a field 5. Move it on header 6. Close window with top right cross => dialog appears to confirm 7. Click Cancel button (so we don't close window) 8. Close window with top right cross (again) 8. Click Don't save button Actual Results: Crash Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 148750 [details] gdb bt
Robert/Alex: thought you might be interested in this one to confirm it.
This is probably a follow on / fallout from the bug where moving any field to the header detail caused a crash (can't remember which one that was though now).
Have tried all the steps. I couldn't reproduce a crash with Version: 6.3.0.0.alpha0+ Build ID: 9bc10964f0673b64e282ad567d08bf7ebba4df65 CPU threads: 6; OS: Linux 4.12; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-27_18:08:30 Locale: de-DE (de_DE.UTF-8); UI-Language: en-US Calc: threaded OpenSUSE 15 64bit rpm Linux.
Thank you Robert for having given a try. I tested again with master sources updated today, it still crashes. Armin: knowing your work on this part, any thoughts about the bt attached?
@Julien : no repro for me with Version: 6.3.0.0.alpha0+ Build ID: e9db8eceff48290be72591f7422b4fc45e5752fc CPU threads: 4; OS: Mac OS X 10.14.2; UI render: default; VCL: osx; Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US Calc: threaded using the default "red" close window button on OSX.
Thank you Alex for your feedback. Hope bt I provided will help.
No crash in Version: 6.3.0.0.alpha0+ Build ID: a8f21e120b1073d7019d41e85cc9a15104ed5c93 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 @Julien, still reproducible in master? Could you please create a screencast on how to reproduce the crash ?
On Win7 with master sources updated some days ago, I could reproduce this. I haven't got a bt but noticed these logs on console: warn:svx.uno:7656:10544:svx/source/svdraw/svdobj.cxx:2756: a UNO shape took over an SdrObject previously owned by another UNO shape! warn:svx:7656:10544:svx/source/svdraw/svdmodel.cxx:239: SdrModel::~SdrModel: Not all incarnations of SdrObjects deleted, possible memory leak (!) warn:vcl:7656:10544:vcl/source/window/dialog.cxx:914: Dialog::StartExecuteModal() - Parent not visible
Created attachment 149241 [details] bt with debug symbols
(In reply to Xisco Faulí from comment #8) > ... > > @Julien, still reproducible in master? > Could you please create a screencast on how to reproduce the crash ? I don't know how to do this. Certainly someone will reproduce this or let's close this one.
No crash Version: 6.3.0.0.alpha0+ Build ID: c7ad7849d54fd3dad67e7779102f65b8b2f04881 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Let's not bother everybody with it if I'm the only one to have this bug.