Apache OpenOffice (AOO) Bugzilla – Issue 126221
AOO Base crashes when deleting a line in the SQL editor
Last modified: 2017-05-20 09:36:04 UTC
Context: AOO Base 4.1.1 under Win8.1 and JRE 1.8.0_31. No other AOO (calc,...) document open. Problem encountered several times with real base leading to a data loss. But can be reproduced with a simple test: (1) open AOO Base to create a new local base, (2) open the SQL window with menu tools/SQL, (3) paste from MS Notepad the following SQL query: CREATE TABLE "sa" ( "id_ac" INTEGER, "maj_in" INTEGER, "maj_ac" date, PRIMARY KEY ("id_ac") ); (4) Then delete the whole line 'PRIMARY KEY' with backspaces from the end of line. AOO crashes while deleting the last character and then the LF/CR.
I was not able to reproduce the crash. AOO 4.1.1 and Debian Lxde x64 At step (4) if you remove 'PRIMARY KEY ("id_ac")', SQL syntax is wrong: A comma is present at end of previous line '"maj_ac" date,'
The crash might be system-dependent. Let's see if someone with Win 8.1 can try to reproduce it.
Addendum: here is the Windows event log: Nom de l’application défaillante soffice.bin, version : 4.0.9774.500, horodatage : 0x53d77a01 Nom du module défaillant : MSVCR90.dll, version : 9.0.30729.8387, horodatage : 0x51ea24a5 Code d’exception : 0xc0000417 Décalage d’erreur : 0x0006ccd5 ID du processus défaillant : 0x1790 That suggest a system-dependant problem (Microsoft Virtual C++ lib).
Cannot reproduce in a 32 bit Windows XP SP3 virtual machine with SVN trunk, nor on 64 bit Windows 8.1 with AOO 4.1.2. jl26: have you managed to reproduce it on another system?
No news from author since +90 days. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information: a) Provide a step-by-step procedure to reproduce (the simpler will be the better) b) Provide any test case(s) which will help us confirm the problem (like a sample document) c) Provide screenshots of the problem if you think it might help d) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue.