Crash clicking chart after deleting table
Steps to Reproduce:
1. Open attached file
2. Delete the table
3. Double click the chart -> crash without crash report
Inspired by bug 132714
User Profile Reset: No
Versie: 220.127.116.11 (x64)
Build ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8
CPU-threads: 4; Besturingssysteem: Windows 6.3 Build 9600; UI-render: standaard; VCL: win;
Locale: nl-NL (nl_NL); UI-taal: nl-NL
Created attachment 160394 [details]
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Maybe a dupe of bug 132714
Created attachment 160399 [details]
bt with debug symbols
On pc Debian x86-64 with master sources updated today, I could reproduce this.
Here's the last bt with "catch throw" before the fatal error popup appears.
Let's increase priority since:
- it's a crash
- it's a regression
- it concerns all envs
I can't reproduce it in
Build ID: 1eb6210d678bbb0c875f0f72b...
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); UI: en-US
bibisect-linux64-6.2 repository points to https://cgit.freedesktop.org/libreoffice/core/commit/?id=026e2623f7f498432e6dc970fb06145dfc77dc45 but I'm not 100% sure this is the commit that introduced the problem...
(In reply to Xisco Faulí from comment #6)
> bibisect-linux64-6.2 repository points to
> ?id=026e2623f7f498432e6dc970fb06145dfc77dc45 but I'm not 100% sure this is
> the commit that introduced the problem...
bibisect-win32-6.2 points to the same commit, it's dealing with charts, let's assume it's the responsible commit until there're clues pointing otherwise.
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://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!