Description: A specific sequence of operations results in a Crash dialog when LO is started again after saving a spreadsheet and exiting. The problem seems to depend on the details of how the spreadsheet was modified before it was saved (the modification happens in Basic macros which delete and re-create a sheet). No crash report opens after I click "Send Crash Report". This might be a problem where LO can not make my browser open the crash report page. While I am using a non-standard browser (firefox-esr) I think I have configured my desktop system to use it correctly: The command "xdg-open <url>" works. FWIW I'm running xubuntu 22.04.1 LTS; the desktop uses xfce, not gnome. STEPS TO REPRODUCE: 1. Download both the "t.ods" and "tickers.csv" files and place them in the /tmp directory (tickers.csv *must* be in /tmp -- the test macro is hard-coded to look for /tmp/*.csv) Note: Macro security should be set to "Medium" (prompt each time). 2. /path/to/lo t.ods Enable macros when prompted. 3. Click the yellow "Reload csv" button (the tickers.csv file *must* be in /tmp and no other .csv files in /tmp) 4. File->Save 5. File->Exit 6. /path/to/lo t.ods (crash dialog appears) Note: After clicking through the crash dialogs the spreadsheet opens anyway, so this is odd. Steps to Reproduce: . Actual Results: . Expected Results: . Reproducible: Always User Profile Reset: Yes Additional Info: I did delete $HOME/.config/libreoffice/r/user which is supposed to have profile data (the 'util' directory never re-appeared, so I suspect dev builds store profile somewhere else). I also entered "safe" mode and did "reset to defaults".
Created attachment 183931 [details] Spredsheet needed to reproduce bug (t.ods)
Created attachment 183932 [details] tickers.csv data file which MUST be in /tmp to reproduce the bug
Is the crash dialog supposed to display a "crash signature"? It did not seem to show anything specific. The second "Crash Report" window only shows this: <<Please check the report and if no bug report is connected to the crash report yet, open a new bug report at bugs.documentfoundation.org. Add detailed instructions on how to reproduce the crash and the shown crash ID into the crash report field. Thank you for your help in improving LibreOfficeDev.>> --- Also: The crash only occurs the *first* time LO is started after the spreadsheet is saved. After clicking through the crash dialog and exiting LO, a subsequent start does not cause a crash. It is necessary to click the yellow "Reload csv" button and do Save + Exit, then start again to see another crash.
I downloaded today's "master" build and it always hangs at exit, with a thread blocked in futex_wait. I'll attach backtrace and strace logs. \ Until this is worked out it's hard to investigate the earlier problem. STEPS TO REPRODUCE HANG: $ /path/to/instdir/program/soffice # no arguments File->Exit (hangs) Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4e4a31ac7d920c71e26ca4acd18c11ec2bd015bb CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Created attachment 184196 [details] gdbtrace.log from new hang (see comment #4)
Created attachment 184197 [details] strace.log from new hang (see comment #4)
(In reply to Jim Avera from comment #0) > 3. Click the yellow "Reload csv" button > (the tickers.csv file *must* be in /tmp and no other .csv files in /tmp) I get Inadmissible value or data type. Data type mismatch. Pointing to line 429 in LoadCSV dim BidVal as double : BidVal = CDbl(bid) and specifically highlighting: BidVal = CDbl(bid)
(In reply to Buovjaga from comment #7) > I get > > Inadmissible value or data type. > Data type mismatch. Same, but it points to line 259 for me, in Standard > Functions > NICKELDIME: OptionExpDt = Left(Expiry,3) & " " & Mid(Expiry,4,2) & ", 20" & Mid(Expiry,7,2) Version: 7.5.7.1 (X86_64) / LibreOffice Community Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded (In reply to Jim Avera from comment #3) > Is the crash dialog supposed to display a "crash signature"? It did not > seem to show anything specific. If you are using a daily build, the dialog does not send crash reports. Can you please re-test with a release, e.g. 7.6.2.1, which would allow you to end one?
Hi, Best wishes for the new year! I re-ran the demo using 7.6.2.1 per Stéphane's request. No hangs. After clicking yellow button, save, exit, restart, the crash dialog appeared and I could send a Crash Report. The URL it showed was https://crashreport.libreoffice.org/stats/crash_details/acc00046-4f7a-4b44-8f47-08586d4368a1 which shows a SEGV fault in some hash table code. --- BTW, when I clicked the "Reload CSV" (yellow button) to run the macro, the terminal displayed: ** (soffice:146163): WARNING **: 14:39:52.134: Exception caught processing focus events Note: The macro may well be buggy or the test data incorrect. However user data should not be able to crash LO.
[Automated Action] NeedInfo-To-Unconfirmed