Description: When attempting to edit a database report, I get an immediate crash/hang. Attempting to debug indicates a problem in the UnoAffine bridge. 1) Download the enclosed sample ODB file. 2) Load into LO. 3) Click on the Reports button 4) Right mouse button click on RptTasks and choose Edit from the context menu. 5) Immediate hang/crash Steps to Reproduce: See above Actual Results: Immediate crash / hang and restart of LO application Expected Results: Should not crash, should instead open the Report for editing. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 847a8e065f0b35fdab637f6f5abfb1be82a262d7 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded
Created attachment 174551 [details] LLDB backtrace
Created attachment 174552 [details] Sample ODB file containing report
*** This bug has been marked as a duplicate of bug 117159 ***
Is this really a duplicate of bug 117159? The backtraces are different and the described behaviour leading to the crash is different. In this report, simply opening the report in Edit mode causes the crash, whereas in bug 117159 the crash is caused when attempting to edit a chart object.
Created attachment 174576 [details] GDB trace of crash Interestingly, it only crashes for me with a --backtrace session (dbgutil build). I guess it's close enough. Arch Linux 64-bit Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 67879304f61252838a6b2e2549d7205b445776f8 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 27 August 2021
Doesn't crash for me on Windows using 7.2.1.1 and today's master (dbgutil).
Not reproducible in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 4f4452f6a74201e862971a79ba5bdcd06f3ba9ce CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Mike and Xisco: are you running under GDB?
(In reply to Buovjaga from comment #8) > Mike and Xisco: are you running under GDB? Yes, it crashes only if I use --backtrace Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: d5ade739771ddf06cc7ee6d4af15672bfcf09ed6 CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF-dbg, Branch:master, Time: 2021-08-31_22:17:16 Calc: threaded Not sure whether it's related to the original report though. Alex, are you using a ARM build? then this issue is related to bug 144130
(In reply to Xisco Faulí from comment #9) > Not sure whether it's related to the original report though. > Alex, are you using a ARM build? then this issue is related to bug 144130 Hi Xisco, No, the 7300alpha build I have is for x86_64.
Alex: would be nice, if you could bibisect this.
Not sure what to do about this now. In normal use, I tried switching JDKs (from 12 to 14) to see if that would make any difference, and now I don't get an immediate crash. Even switching back to the previously used JDK no longer causes a crash. Only in a debug session do I get the immediate crash (and the bt I've already uploaded), as confirmed by Buovjaga.
Repro 5.2 and 7.4+. I remove regression until it's explained.