Issue 109770 - ChartView::getExplicitValuesForAxis accessing destroyed VCoordinateSystem
Summary: ChartView::getExplicitValuesForAxis accessing destroyed VCoordinateSystem
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: chart (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: lars.langhans
QA Contact: issues@graphics
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-03 13:08 UTC by Stephan Bergmann
Modified: 2013-02-24 21:20 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
stack trace (5.46 KB, text/plain)
2010-03-03 13:08 UTC, Stephan Bergmann 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Stephan Bergmann 2010-03-03 13:08:16 UTC 
Executing chart2/qa/unoapi on DEV300_m72-based CWS sb118 unxlngi6 non-pro once
caused OOo to crash with the attached stack trace. 
(m_aSecondaryExplicitScales.begin() at VCoordinateSystem.cxx:350 causing an
STLport assertion probably indicates that this VCoordinateSystem instance is
already destroyed.)
Comment 1 Stephan Bergmann 2010-03-03 13:08:51 UTC 
Created attachment 68128 [details]
stack trace
Comment 2 Stephan Bergmann 2010-04-19 16:15:30 UTC 
Executing chart2/qa/unoapi on DEV300_m76-based CWS sb120 (follow-up to CWS
sb118) on wntmsci12 non-pro gives very many "SolarMutex not locked, and not
thread save code in VCL is called from outside of the main thread" messages
(from vcl/win/source/app/salinst.cxx).  This indicates that there are probably
race conditions in the code, which might explain the crash.  Issue 110253 might
have the same problem.

For now, worked around by disabling the automatic (via subsequenttests)
execution of chart2/qa/unoapi as
<http://hg.services.openoffice.org/cws/sb120/rev/7bb7cfbade97>; please revert
once the problem is fixed.
Comment 3 IngridvdM 2010-06-01 16:32:34 UTC 
Within CWS chart47 several problems around the chart uno api tests where fixed.
Especially the "SolarMutex not locked" assertions were fixed.
The exact reason for this special issue was not found but it didn't appear
again, so I set it to fixed and enable the tests again.
Comment 4 IngridvdM 2010-06-03 12:05:48 UTC 
@lla, please verify in CWS chart47 that the api tests are enabled again in
chart2/prj/build.lst and that the api test runs without error in module chart2.
Thanks!
Comment 5 lars.langhans 2010-06-04 14:05:20 UTC 
verified.
Comment 6 lars.langhans 2010-11-15 12:49:51 UTC 
close