Bug 847519

Summary: [fix available] segfault at chart creation in lcl_getExplicitSimpleCategories
Product: Red Hat Enterprise Linux 6 Reporter: David Jaša <djasa>
Component: libreofficeAssignee: -RETIRED- <erack>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: caolanm, dtardon, tpelka
Target Milestone: beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libreoffice-3.4.5.2-18.el6 Doc Type: Bug Fix
Doc Text:
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.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 10:03:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 960054    
Attachments:
Description Flags
reproducer
none
backtrace with java provided by gcj
none
valgrind output with java provided by gcj
none
backtrace with java provided by sun java 1.6
none
valgrind output with java provided by sun-java
none
valgrind output with java provided by sun-java (hsPID file by valgrind)
none
patch solving the problem none

Description David Jaša 2012-08-12 15:02:33 UTC
Created attachment 603789 [details]
reproducer

Description of problem:


Version-Release number of selected component (if applicable):
libreoffice-core-3.4.5.2-16.1.el6_3.x86_64

How reproducible:
always

Steps to Reproduce:
1. open attached file in Calc
2. select B2:T30
3. click "chart" icon or go to Insert -> Chart
  
Actual results:
lo segfaults

Expected results:
lo continues running

Additional info:
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

Comment 1 David Jaša 2012-08-12 15:03:27 UTC
Created attachment 603790 [details]
backtrace with java provided by gcj

Comment 2 David Jaša 2012-08-12 15:04:35 UTC
Created attachment 603791 [details]
valgrind output with java provided by gcj

Comment 3 David Jaša 2012-08-12 15:11:02 UTC
Created attachment 603792 [details]
backtrace with java provided by sun java 1.6

Comment 4 David Jaša 2012-08-12 15:19:45 UTC
Created attachment 603793 [details]
valgrind output with java provided by sun-java

Comment 5 David Jaša 2012-08-12 15:20:59 UTC
Created attachment 603794 [details]
valgrind output with java provided by sun-java (hsPID file by valgrind)

Comment 6 Caolan McNamara 2012-08-13 10:23:46 UTC
Reading the backtraces, where #3 is the most useful one, this appears to be similar to bug 699284 and bug 657807

Comment 7 David Tardon 2012-08-15 07:35:15 UTC
I cannot reproduce the crash with libreoffice-3.4.5.2-18.fc16 .

Comment 8 David Tardon 2012-08-15 08:28:54 UTC
Does not crash with libreoffice-core-3.4.5.2-16.el6 either.

Comment 9 David Tardon 2012-08-16 13:51:24 UTC
The 2nd step of Steps to Reproduce should be "select A1:T30". It crashes 3.4, 3.5 is okay. MALLOC_CHECK_ is irrelevant.

Comment 10 RHEL Program Management 2012-09-07 05:22:35 UTC
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.

Comment 11 -RETIRED- 2013-02-19 19:51:26 UTC
Created attachment 699615 [details]
patch solving the problem

Comment 17 errata-xmlrpc 2013-11-21 10:03:12 UTC
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.

http://rhn.redhat.com/errata/RHBA-2013-1594.html