Issue 103025 - Runtime Error in MS Visual C++ Runtime Library
Summary: Runtime Error in MS Visual C++ Runtime Library
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Calc
Classification: Application
Component: editing (show other issues)
Version: OOO310m11
Hardware: HP (PA-RISC) Windows XP
: P2 Trivial (vote)
Target Milestone: ---
Assignee: spreadsheet
QA Contact: issues@sc
URL:
Keywords: crash
Depends on:
Blocks:
 
Reported: 2009-06-23 08:22 UTC by andreas17
Modified: 2010-01-26 06:01 UTC (History)
4 users (show)

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


Attachments
OpenOffice 3.1 Runtime Error (20.13 KB, text/plain)
2009-06-23 08:24 UTC, andreas17
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description andreas17 2009-06-23 08:22:58 UTC
How to reproduce the bug:
1. Create a file.odb containing queries.
   These queries accesses a MySQL DB via MySQL ODBC 5.1 Driver
   (I need it to search our BugZilla database)
2. Create a file.ods and add some crosstables via DataPilot using such queries
   I have four such tables in one sheet and 7 sheets having different tables
3. Save the file
4. Refresh the cross tables
5. Insert rows between two tables using the button "Insert Rows"
-> the second try lets crash OpenOffice by the following Error message box:
-------------------------------------------------------------------------------
Microsoft Visual C++ Runtime Library
Runtime Error!
Program: C:\Program Files\OpenOffice.org.3\program\soffice.bin
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information
-------------------------------------------------------------------------------
Sometime I need more tries.
Due to the fact that I press the save button very often I've never lost data.
Comment 1 andreas17 2009-06-23 08:24:08 UTC
Created attachment 63160 [details]
OpenOffice 3.1 Runtime Error
Comment 2 chojin 2009-06-26 08:52:04 UTC
I can confirm this problem:
But the queries used in the .odb file don't have to be MySQL queries. 
I can simulate it using CSV and ODS queries too.

Steps I use to reproduce:
- create an ODB file containing queries of any form (native, CSV, ODS, mysql, ..)
- create an OSD file and add a DataPilot using the query as the source
- select a block of cells somewhere in the file and remove the cells, moving the
other cells up or left
- insert or remove one or more rows or columns somewhere in the file
- repeat last 2 steps a few times

after repeating those last 2 steps a few times I've seen following different
behaviours:
- OOo stops responding, using full CPU and needs to be killed
- OOo pauses for a while, then starts reponding again but doesn't refresh the
screen (inserted or deleted rows/columns or cell-blocks are still shown) until
the deleted cells are scrolled out of sight and back. Any subsequent
removing/adding of cells/rows/collumns then show the same behaviour. And when
window is closed, OOo crashes completely with the Visual C++ Runtime error.

Please set this issue to a higher priority, and consider it as a blocker for
3.1.1? As it makes one of the great powers and features of Calc unusable and
undependable and should be resolved asap. A few users here already lost valuable
data because of those crashes.
Comment 3 Olaf Felka 2009-06-26 09:27:08 UTC
@ msc: Please have a look.
Comment 4 marc.neumann 2009-06-26 11:50:42 UTC
Hi all,

I can reproduce this also with the simple Bibliography bilio table. But only in
OOO310 m11 (OOO 3.1) NOT in OOO310_m13 which will be the OOO3.1.1. So I assume
that this issue is already fixed.

Can someone else confirm this also. The OOO310_m13 should be available as
download in the next days.

Bye Marc
Comment 5 Mechtilde 2009-07-12 20:20:51 UTC
worksforme -> closed
Comment 6 Mechtilde 2009-07-12 20:22:23 UTC
worksforme -> closed
Comment 7 robbk 2010-01-25 14:26:18 UTC
We are experiencing similar problems in OOo 3.1.0.
If we select several cells in a DataPilot and copy and paste them into a new
table in the same document, then do this several times or insert rows in the
table we copied the data into, then we get the C++ Runtime Error, but not always.
Copying the data into a new document is our workaround at the moment.
Will wait and hope the problem is fixed in 3.1.1.
Comment 8 niklas.nebel 2010-01-25 15:18:59 UTC
robbk, yes, you should try 3.1.1. This sounds similar to issue 101725.
Comment 9 robbk 2010-01-26 06:01:59 UTC
nn, yes, except that with us, the document doesn't freeze. It immediately
displays the C++ Runtime Error.