Bug 91357 - Base freezes after few minutes
Summary: Base freezes after few minutes
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
4.4.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-18 12:32 UTC by christian_kuhn
Modified: 2015-06-11 14:40 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
example database (196.81 KB, application/vnd.oasis.opendocument.database)
2015-05-19 15:09 UTC, christian_kuhn
Details
Backtrace of crash (7.01 KB, text/plain)
2015-05-22 08:35 UTC, Buovjaga
Details
an example for a file input / output error (26.20 KB, image/png)
2015-05-26 23:05 UTC, christian_kuhn
Details
error message because a form was damaged (43.68 KB, image/png)
2015-05-26 23:11 UTC, christian_kuhn
Details
data could not be read from manifest.rdf (6.84 KB, image/png)
2015-05-30 17:17 UTC, christian_kuhn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description christian_kuhn 2015-05-18 12:32:24 UTC
Hello,

I have inserted a lot of data using LibreOffice Base via a form into an internal HyperSQL database. After few minutes (approx. 15 - 30 min) LibreOffice becomes very slowly and freezes. When it becomes slowly, the  database file enlarges. It is no longer possible to insert new data via the form or to interact with LibreOffice, so I must kill the application.

Christian
Comment 1 raal 2015-05-19 06:43:51 UTC
Hello Christian,

Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. Please attach also sample data.
I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive information before attaching it.)
How can I eliminate confidential data from a sample document?
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
Thank you
Comment 2 christian_kuhn 2015-05-19 15:09:38 UTC
Created attachment 115720 [details]
example database

Example database for the bug. It happens more randomly, not so systematically. It happens, if I have more than one form opened (3 - 4 forms) and want read data from one form and put new data into another form. In such a case I cannot save the new unsaved data within the form and get a "file input / output error" if I try to save the data when I close the form. But (sometimes, when LibreOffice do react) I can still save the database file. After closing Base, the database file is approx. 20 - 30 % larger than before.
Comment 3 christian_kuhn 2015-05-19 15:12:48 UTC
Hello,

I have attached a simple example, hope, it works. 

Christian
Comment 4 Buovjaga 2015-05-22 08:23:25 UTC
If I open a form (not edit) and change the Nr. and try to save, it says:

Error updating the current record.

Violation of unique constraint SYS_PK_51: duplicate value(s) for column(s) "Nr." in statement [UPDATE "Table_2" SET "Nr." = ? WHERE "Nr." = ?]

I think this is something different. I do not get any crash or other errors.

Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+
Build ID: 83eb114394879cbfd073322a51c47d02553c1fcf
TinderBox: Win-x86@39, Branch:master, Time: 2015-05-22_06:33:51
Locale: fi-FI (fi_FI)
Comment 5 Buovjaga 2015-05-22 08:35:58 UTC
Created attachment 115802 [details]
Backtrace of crash

Correction: a crash occurs with this:
1. Open the file
2. Double click a form to open it
3. Close form
4. Close file
Comment 6 christian_kuhn 2015-05-22 13:22:00 UTC
Hello Beluga,


> If I open a form (not edit) and change the Nr. and try to save, it says:
> 
> Error updating the current record.
> 
> Violation of unique constraint SYS_PK_51: duplicate value(s) for column
> (s) "Nr." in statement [UPDATE "Table_2" SET "Nr." = ? WHERE "Nr." = ?]  


I think, this is ok. I get this, if a second data set has the same value for "Nr." as in the form because "Nr." is the primary key in table. 

The "file input / output error" appears only, if Base becomes slowly and freezes. I don't know, what happens.

The failed instruction in the backtrace seems to be the same as in the second backtrace of bug 91338.

Christian
Comment 7 Buovjaga 2015-05-22 13:29:49 UTC
(In reply to christian_kuhn from comment #6)
> The failed instruction in the backtrace seems to be the same as in the
> second backtrace of bug 91338.

Ok, then I have to set back to unconfirmed :(
Comment 8 christian_kuhn 2015-05-26 23:05:53 UTC
Created attachment 116066 [details]
an example for a file input / output error

This is an example for a "file input output error" which occurs, when Base freezes.
Comment 9 christian_kuhn 2015-05-26 23:11:54 UTC
Created attachment 116067 [details]
error message because a form was damaged

After reopening database, a form was damaged. I have got an error message.
Comment 10 christian_kuhn 2015-05-30 17:17:58 UTC
Created attachment 116182 [details]
data could not be read from manifest.rdf

It seems, that forms are damaged, if a "file input / output error" occured previously. I have got this message, that data could not be read from manifest.rdf (locale: german), after LibreOffice was frozen and a "file input / output error" occured. After this message, I could still open the form, but another time forms are really damaged, and I could not open them. I am sure, that the file system is not wrong or corrupt. I have got this with LO 4432 and an internal HSQLDB.
Comment 11 Alex Thurgood 2015-06-09 16:04:18 UTC
The OpenOffice.org forums are replete with reports like this. It is not new behaviour, and happens, seemingly in an unsystematic manner with embedded hsqldb database files.

The main constants of this kind of report seem to be :
- inserting lots of records in one session ;
- the stack at some stage gets corrupted, causing LO to either quit, or forcing the user to kill LO in order to regain control ;
- as a consequence of the crash or forced quit, the ODB files become huge and are corrupted.


@Christian : without a systematic reproducible way of obtaining the same screwed up ODB file, this bug will remain unconfirmed, and eventually, closed. Unfortunately, there is probably very little you can do about it (or anyone else for that matter)

Your ODB file has become corrupt, and either you have a backup which you can go back to, or else you have essentially lost your data. It may, or may not be possible, to create a new "blank" ODB file and copy over the tables and forms, and queries from the corrupt file to that new ODB file from within LO.

 http://en.libreofficeforum.org/node/7411

https://forum.openoffice.org/en/forum/viewtopic.php?f=13&t=77095&p=351985&hilit=+corrupt+base#p351809