Cause: Chart code accessing out of range values in certain scenarios
Consequence: Crash on creating certain charts
Fix: Clip range to valid range
Result: No crash on creating charts.
Created attachment 603789 [details]
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open attached file in Calc
2. select B2:T30
3. click "chart" icon or go to Insert -> Chart
lo continues running
Most of the traces were captured with: MALLOC_CHECK_=1, MALLOC_PERTURB_=$(($RANDOM % 255 + 1)) and G_SLICE=always-malloc,debug-blocks but I can reproduce it with MALLOC_PERTURB_ and G_SLICE undefined
Created attachment 603790 [details]
backtrace with java provided by gcj
Created attachment 603791 [details]
valgrind output with java provided by gcj
Created attachment 603792 [details]
backtrace with java provided by sun java 1.6
Created attachment 603793 [details]
valgrind output with java provided by sun-java
Created attachment 603794 [details]
valgrind output with java provided by sun-java (hsPID file by valgrind)
Reading the backtraces, where #3 is the most useful one, this appears to be similar to bug 699284 and bug 657807
I cannot reproduce the crash with libreoffice-18.104.22.168-18.fc16 .
Does not crash with libreoffice-core-22.214.171.124-16.el6 either.
The 2nd step of Steps to Reproduce should be "select A1:T30". It crashes 3.4, 3.5 is okay. MALLOC_CHECK_ is irrelevant.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Created attachment 699615 [details]
patch solving the problem
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.