Bug 96938 - EDITING - ODB file crashes when editing tables, queries, forms....
Summary: EDITING - ODB file crashes when editing tables, queries, forms....
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
4.4.7.2 release
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace, regression
Depends on:
Blocks:
 
Reported: 2016-01-07 02:17 UTC by John Tennant
Modified: 2016-06-14 08:01 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
bt on master (29.90 KB, text/plain)
2016-01-07 14:49 UTC, Alex Thurgood
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Tennant 2016-01-07 02:17:13 UTC
LibreOffice crashes when using the attached .odb file.  Base will open the file but as soon as I try do anything (access a table, query, form...), all LibreOffice windows will close without any error message, and when I restart LibreOffice it opens in recovery mode.

Crashes with LibreOffice 4.4.7.2 on Ubuntu 14.04 (my work computer)
Does not crash with 4.4.3.2 on Windows 8.1 (my home computer)

This error appeared some months ago, probably around the update from 4.4.3 to 4.4.4, but I did not report it because I have a work around.

I haven't updated my Windows LibreOffice because I use this database file for work quite regularly and I don't want to lose my work around.  However, I want to use this database at work, so this crash is a bit inconvenient.
Comment 1 frofa 2016-01-07 07:03:35 UTC
For what it's worth, I have been able to successfully open the database "ER Test Database.odb" (attached to the duplicate bug report #96937) in 'split' mode under HSQLDB v2.3 / Mac OSX 'El Capitan' / LibreOffice v5.0.4.2. No problem with opening tables, queries, forms and reports - EXCEPT for the report titled 'Collection Info for labels' which seems to be damaged because running or trying to edit it causes a GENERAL ERROR. Maybe there is something wrong with the original ZIP container file which effects just this one report?
Comment 2 V Stuart Foote 2016-01-07 13:15:38 UTC
see attachment 121759 [details]
Database file that crashes
Comment 3 Alex Thurgood 2016-01-07 14:20:10 UTC
No repro 

Version: 5.2.0.0.alpha0+
Build ID: 5f981642889b1b9980e98ebccc3150e022a73bed
CPU Threads: 2; OS Version: -; UI Render: default; 
Locale : fr-FR (fr.UTF-8)


OSX 10.11.2
Comment 4 Alex Thurgood 2016-01-07 14:23:48 UTC
(In reply to Alex Thurgood from comment #3)
> No repro 
> 
> Version: 5.2.0.0.alpha0+
> Build ID: 5f981642889b1b9980e98ebccc3150e022a73bed
> CPU Threads: 2; OS Version: -; UI Render: default; 
> Locale : fr-FR (fr.UTF-8)
> 
> 
> OSX 10.11.2

I can load the ODB file, and open tables, forms, etc.

I get a systematic crash on shut down of LibreOffice though, with this file.
Comment 5 Alex Thurgood 2016-01-07 14:27:19 UTC
After loading the same file with LO5032, I get the following error when trying to clikc on any of the left hand pane icons of the main db window:

Statut SQL: HY000

La connexion n'a pas pu être établie. La base de données a été créée par une version plus récente de LibreOffice.

Bizarre.
Comment 6 Alex Thurgood 2016-01-07 14:31:07 UTC
My master build must have corrupted the file in some way when I shut down. If I download the ODB file again, and re-open in LO5032, I can open the tables, forms, etc.

So this is WFM in

Version: 5.0.3.2
Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75
Locale : fr-FR (fr.UTF-8)

OSX 10.11.2
Comment 7 Alex Thurgood 2016-01-07 14:32:10 UTC
@Lionel : this is a weird one
Comment 8 Alex Thurgood 2016-01-07 14:40:43 UTC
OK, so if I open this ODB file in my master build with lldb running, I see this :

warn:unoxml:45295:13:unoxml/source/dom/documentbuilder.cxx:296: libxml2 error: Extra content at the end of the document
Line: 544
Column: 1

Note that I see this after having attempted to change the first record in the very first table and seein LOdev bomb out on me when I tried to save the change or close the table window (I ignored the auto-recovery). If the file wasn't already corrupted, it has now become so. Will need to check by downloading a clean copy of the file to test again in lldb.
Comment 9 Alex Thurgood 2016-01-07 14:48:48 UTC
This is the output when attempting to save a change to the first record of the first table :
warn:vcl:45295:1:vcl/source/window/mouse.cxx:472: Window::ReleaseMouse(): window doesn't have the mouse capture
warn:legacy.osl:45295:1:include/cppuhelper/interfacecontainer.h:479: object is disposed
warn:legacy.osl:45295:1:include/cppuhelper/interfacecontainer.h:479: object is disposed
warn:legacy.osl:45295:9:connectivity/source/drivers/hsqldb/HStorageAccess.cxx:369: No Seekable stream!
warn:legacy.osl:45295:9:connectivity/source/drivers/hsqldb/HStorageAccess.cxx:221: Input stream is NULL!
2016-01-07T15:41:48.504+0100  SEVERE  DataFileCache.setFileModified
java.io.IOException: Stream is not valid
	at com.sun.star.sdbcx.comp.hsqldb.NativeStorageAccess.read(Native Method)
	at com.sun.star.sdbcx.comp.hsqldb.StorageAccess.readInt(StorageAccess.java:66)
	at org.hsqldb.persist.RAStorageWrapper.readInt(Unknown Source)
	at org.hsqldb.persist.DataFileCache.setFileModified(Unknown Source)
	at org.hsqldb.persist.DataFileCache.saveRows(Unknown Source)
	at org.hsqldb.persist.Cache.saveRows(Unknown Source)
	at org.hsqldb.persist.Cache.saveAll(Unknown Source)
	at org.hsqldb.persist.DataFileCache.defrag(Unknown Source)
	at org.hsqldb.persist.Log.defrag(Unknown Source)
	at org.hsqldb.persist.Log.checkpoint(Unknown Source)
	at org.hsqldb.persist.Logger.checkpointInternal(Unknown Source)
	at org.hsqldb.persist.Logger.checkpoint(Unknown Source)
	at org.hsqldb.StatementCommand.getResult(Unknown Source)
	at org.hsqldb.StatementCommand.execute(Unknown Source)
	at org.hsqldb.Session.executeCompiledStatement(Unknown Source)
	at org.hsqldb.Session.executeDirectStatement(Unknown Source)
	at org.hsqldb.Session.execute(Unknown Source)
	at org.hsqldb.jdbc.JDBCStatement.fetchResult(Unknown Source)
	at org.hsqldb.jdbc.JDBCStatement.execute(Unknown Source)


Process 45295 stopped
* thread #1: tid = 0x61b20a, 0x00000001067c717e libtllo.dylib`DbgUnhandledException(com::sun::star::uno::Any const&, char const*, char const*) + 926, queue = 'com.apple.main-thread', stop reason = signal SIGSEGV
    frame #0: 0x00000001067c717e libtllo.dylib`DbgUnhandledException(com::sun::star::uno::Any const&, char const*, char const*) + 926
libtllo.dylib`DbgUnhandledException(com::sun::star::uno::Any const&, char const*, char const*):
->  0x1067c717e <+926>: movq   0x8(%rcx), %rcx
    0x1067c7182 <+930>: movq   %rcx, -0x80(%rbp)
    0x1067c7186 <+934>: leaq   0xb5935(%rip), %rsi       ; "\ncontext: "
    0x1067c718d <+941>: leaq   -0x88(%rbp), %rdi
Comment 10 Alex Thurgood 2016-01-07 14:49:17 UTC
Created attachment 121782 [details]
bt on master
Comment 11 Alex Thurgood 2016-01-07 14:49:43 UTC
(In reply to Alex Thurgood from comment #10)
> Created attachment 121782 [details]
> bt on master

and confirming
Comment 12 Alex Thurgood 2016-01-07 14:55:28 UTC
I can't get it to crash on LO5032, I can edit record data in the tables, save and quit no problem.
Comment 13 Alex Thurgood 2016-01-07 15:13:46 UTC
Sorry, setting back to unconfirmed, I can't reproduce this on 

Version: 4.4.7.2
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: fr.UTF-8

OSX 10.11.2

I will consider opening a separate report for my findings on master.
Comment 14 Julien Nabet 2016-01-07 19:01:02 UTC
On pc Debian x86-64 with master sources updated today, I got no crash with tables , queries and forms but had a crash with reports.
soffice.bin: /home/julien/compile-libreoffice/libreoffice/xmloff/source/core/nmspmap.cxx:264: rtl::OUString SvXMLNamespaceMap::GetQNameByKey(sal_uInt16, const rtl::OUString&, bool) const: Assertion `false' failed.
(so the same as tdf#94355)

However, when I tried to add a row in table, I couldn't, it hanged with lots of these:
warn:legacy.osl:22872:1:svtools/source/brwbox/brwbox3.cxx:378: Illegal call here!
then these
** (soffice:22872): WARNING **: Focused object has invalid index in parent
Comment 15 Alex Thurgood 2016-01-08 16:43:10 UTC
So it does crash/hang when attempting to edit a rowset on master, which is what I found too on OSX
Comment 16 Alex Thurgood 2016-01-14 09:35:31 UTC
(In reply to V Stuart Foote from comment #2)
> see attachment 121759 [details]
> Database file that crashes

This file is corrupted or has an incomplete XML stream (probably some mismatched tags)

ns1:~ alex$ zip -T /Users/alex/Downloads/ER\ Test\ Database\(4\).odb 
reports/Obj11/settings.xml  bad CRC 6ca9dad9  (should be 0e002e59)
  error:  invalid compressed data to inflate forms/Obj61/Configurations2/accelerator/current.xml
test of /Users/alex/Downloads/ER Test Database(4).odb FAILED

zip error: Zip file invalid, could not spawn unzip, or wrong unzip (original files unmodified)


We have had bug reports in the past where various ODB files have been corrupted - perhaps this is a duplicate of one of those reports, but they always seem to get closed for one reason or another (mostly reproducibility, it seems).
Comment 17 John Tennant 2016-01-16 05:10:03 UTC
Today I installed LibreOffice 4.4.7.2 on a Windows 7 laptop and confirmed that my .odb file will open and can be edited.  Using the exact same .odb file (on a USB flash memory), LibreOffice 4.4.7.2 on Ubuntu 14.04 crashes as described. 

The .odb file may be corrupt but if so, it appears Windows is more forgiving than Ubuntu.  

With the Ubuntu crash no .lck file is created.  Don't know if this useful info...
Comment 18 Alex Thurgood 2016-06-14 08:01:18 UTC
In a report I was triaging yesterday, file corruption was reported as occurring with LO 4472 on an Ubuntu provided version. I am going to close this particular report as notourbug, as it seems that the distrib-specific version is at fault. No repro on Windows or Mac with corresponding versions.