Apache OpenOffice (AOO) Bugzilla – Issue 14197
Bibliography database crashes when 'clicking around'
Last modified: 2017-05-20 08:53:25 UTC
The bibliography database entry UI crashes quite often during normal work. Here's one way to produce a crash: - start writer - Tools -> Bibliography database - 'title' and 'author' fields are too short as 'VARCHAR', so I changed them to type Memo (LONGVARCHAR) I did this in the very beginning, so unluckily I cannot tell whether this is related to the crash - as of now, I have four entries in the bibliography database - arbitrarily click the four empty fields to the left of each entry - eventually the program will crash - seems there's quite a number of ways to make it crash - just caused one by accidentially duplicating an entry in the database and then deleting it again - The error message is always identical (C++ debugger): Unhandled exception in soffice.exe (SAL3.DLL): 0xC0000005: Access violation Please let me know, if you need any more information Best regards Oliver
I am not sure that this could be considered an defect. Changing the structure of the database would normally cause the applications using it to crash. Also I would not consider changing the structure of an application's database as 'normal work' more like 'hacking' (no offense intended). However, the bibliographic code could do more tests to check the structure of the database before starting, and issue an error message "The user appeares to have changed my database, I will not start until he/she has fixed my code as well" I have reassigned it to the database group to consider code changes
Hi, two more comments from me: I agree that allowing the user to dynamically change the DB layout might cause a lot of trouble. But if that is the case the user should not be given this possibility at all. At least when it comes to the bibliography fields 'author' and 'title', the type 'VARCHAR' is way too short. None of the titles (or author lists resp.) I wanted to enter would fit into VARCHAR. That's why I changed the field type to LONGVARCHAR. If this was not possible, the whole bibliography functionality would be useless (which would be a bloody shame, as it's one of the best features in OO). Cheers Oliver
Hi Frank, is still OS the owner of the implementation? - Dirk
yes
OS->FS: The only stack I could create is one for you. (from an assertion in alloc.c ) > ntdll.dll!77f767cd() dbase644mi.dll!1c8c278d() file644mi.dll!1d709ac4() file644mi.dll!1d709ee9() dbase644mi.dll!1c8a9e95() dba644mi.dll!1c815299() dba644mi.dll!1c7e4123() dba644mi.dll!1c7b2a06() dba644mi.dll!1c7b785b() dba644mi.dll!1c7bacc5() dl644mi.dll!1d160c60() dl644mi.dll!1d159d92() dl644mi.dll!1d15b6d2() svt644mi.dll!BrowseBox::ImplPaintData() + 0x251 C++ svt644mi.dll!BrowseBox::PaintData() + 0x7f C++ svt644mi.dll!BrowserDataWin::Paint() + 0x35 C++ vcl644mi.dll!2285353c() abababab()
I could also reproduce this with 1.1 Beta, but not with a SRX644m13s2 build, which is pretty near to what will be 1.1 Beta 2. Lundspund, could you please check this again as soon as Beta 2 is out?
@David > However, the bibliographic code could do more tests to check the > structure of the database before starting, and issue an error > message please submit an RFE for this. I myself don't have an opinion here, as the Bibliography really is part of the Writer functionality (which, by chance, uses database access functionality :).
@Lundspund > At least when it comes to the bibliography fields 'author' > and 'title', the type 'VARCHAR' is way too short you might want to submit an RFE for this, too - owner would be tv@openoffice.org, member of the Extras team, which provides the pre-installed Bibliography database.
> I am not sure that this could be considered an defect. > Changing the structure of the database would normally cause the > applications using it to crash. My opinion (there are others :): Every crash, by definition, is a defect - a heavy one. An application should be able to recover from nearly everything you feed it with (at the worst with simply doing nothing, and the best with presenting the user with the problem and allowing him/her to solve it).
> My opinion (there are others :): Every crash, by definition, is a > defect - a heavy one. Agree. I'm trying to introduce OO here at the institute to replace MS Office in the long run - every crash makes that more difficult (and it plays absolutely no role during that process that MS Office crashes just as often... :( Will test again as soon as 1.1 beta 2 is out. Thanks all Oliver
Changed issue status to 'Later', as I started getting mails. Will turn back when 1.1 beta2 is out. Thanks Oliver