Created attachment 117439 [details] Database for testing image-input For reproduction of this bug you must have some photos from a digicam. I have tested this with some photos 3 MB. Open the attached database. Open the form. Write down for Text: '1' Insert the first image by dubbleclick on the imagecontrol. Goto next record. It fails here when trying to insert image 4. Could be you could insert some more images. It doesn't go to next record but throws an error: java.lang.NullPointerException Cancel the last insert. Close the form. Try to open the table. No data could be loaded - same error is reported. Close the Base-file. Reopen the Base-file. No data in the table, but there were saved 3 rows before. (Remark: This 3 rows would be saved if using LO 3.5 - afterwords the file will be reset automatically by SHUTDOWN COMPACT) The error appears in all LO-versions. So I set this on Inherited From OOo. My System: OpenSUSE 13.2 64bit rpm Linux, different LO-Versions, tested also with LO 4.4.4
Created attachment 117440 [details] Screenshot first NullPointerException Note: The exception is thrown by 4th record. It depends on how big the images are.
Created attachment 117441 [details] Screenshot of second NullPointerException Table could not be opened. When closing Base all data since last opening of the file were lost.
On Master 5.1 alpha, OSX 10.10.4, I don't a NullPointerException, but I do see the "java.io.IOException: Stream is not valid" error message. This occurs when attempting to validate a 4.4Mb image insert into the control. Unfortunately, clicking on "More" brings no further information. If I click on "OK", it removes the error message, but then I can do nothing else with the form, if I try to navigate forward or backwards, I get the same error message again. Attempting to Save or Create New tuple also displays the same error message If I try to close the Form, I get the message telling me that the data in the form has changed, do I want to save ? Answering yes, throws the same error message, answering No brings me back to the main odb interface. If I then close the ODB window, LO dies and displays Apple Crash Report Confirming
If I try to recover the file on next LO launch, the file contains none of the previously entered data, it is essentially "clean".
My tests with 3.5 to 5Mb images caused the failure at the second insert.
Attempting to open the Form in LO 4341 or 4332 causes an instant abort. JDK version 1.8.0_45
With LO 3672 and JDK 1.6.0_65, I can insert up to 4 images, and then it fails with the message Robert posted.
(In reply to Alex Thurgood from comment #7) > With LO 3672 and JDK 1.6.0_65, I can insert up to 4 images, and then it > fails with the message Robert posted. If I cancel the failed insert using the Reverse button in the toolbar, then close the form, none of the previously entered data is saved. Any attempt to open the corresponding table results in a select failure.
In Version: 5.1.0.0.alpha1+ Build ID: e2281331b1ab40288494ab3659d9c66e13d3e905 Locale : fr-FR (fr.UTF-8) JDK 1.8.0_51 loading the form from lldb leads to a stopped process while attempting to read the autoincrement value from the first field : * thread #25: tid = 0xcb1e1, 0x000000012fc03fd7, stop reason = signal SIGBUS frame #0: 0x000000012fc03fd7 -> 0x12fc03fd7: testl -0x24e88fdd(%rip), %eax 0x12fc03fdd: retq 0x12fc03fde: movl 0xc(%r12,%rbx,8), %r13d 0x12fc03fe3: jmp 0x12fc03f2f
Stepping through the inserts, lldb spits this out when moving to next record : warn:legacy.tools:5807:1:vcl/inc/svdata.hxx:389: object deleted while in use !
Closing the Form, then attempting to close the ODB file leads to another stoppage : Process 5807 stopped * thread #25: tid = 0xcb1e1, 0x000000012fa1fa6e, stop reason = signal SIGSEGV frame #0: 0x000000012fa1fa6e -> 0x12fa1fa6e: movl 0x8(%rcx), %edx 0x12fa1fa71: shlq $0x3, %rdx 0x12fa1fa75: movq -0x20(%rbp), %r13 0x12fa1fa79: testq %r13, %r13 Process 5807 resuming warn:legacy.osl:5807:1:include/cppuhelper/interfacecontainer.h:479: object is disposed warn:legacy.osl:5807:1:include/cppuhelper/interfacecontainer.h:479: object is disposed warn:legacy.osl:5807:1:include/cppuhelper/interfacecontainer.h:479: object is disposed warn:legacy.osl:5807:1:include/cppuhelper/interfacecontainer.h:479: object is disposed warn:legacy.osl:5807:1:include/cppuhelper/interfacecontainer.h:479: object is disposed Then LOdev has to be closed from the Dock via the menu entry Quit : warn:legacy.osl:5807:1:include/cppuhelper/interfacecontainer.h:479: object is disposed warn:legacy.osl:5807:1:include/cppuhelper/interfacecontainer.h:479: object is disposed warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:legacy.tools:5807:1:basic/source/sbx/sbxobj.cxx:98: Object element with dangling parent warn:sal.osl.pipe:5807:1:sal/osl/unx/pipe.cxx:395: shutdown() failed: Socket is not connected warn:sal.osl.pipe:5807:3:sal/osl/unx/pipe.cxx:436: accept() failed: Software caused connection abort warn:legacy.osl:5807:1:unotools/source/config/configmgr.cxx:168: OSL_ASSERT: items_.empty() Process 5807 exited with status = 0 (0x00000000) (lldb)
Created attachment 117557 [details] bt on master
On pc Debian x86-64 with master sources updated yesterday, I could reproduce this. Here's the detail of the message: Statut SQL: S1000 Code d'erreur: 98 java.io.IOException: java.lang.NullPointerException in statement [INSERT INTO "Table" ( "Image","Text") VALUES ( ?,?)] I noticed too on console: warn:vcl.window:18296:1:vcl/source/window/window.cxx:3426: ignoring RuntimeException "unsatisfied query for interface of type com.sun.star.datatransfer.clipboard.XClipboard!"
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Nothing changed for LO 5.2.2.2 on OpenSUSE 42.1 64bit rpm Linux.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Tested again with Version: 6.0.0.3 Build-ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: kde4; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group Bug hasn't changed in OpenSUSE 42.2 64 bit rpm Linux.
Bug still exits in LO 6.1.5.2 on OpenSUSE 15, 64bit rpm Linux.
Note: With Firebird you could "save" as much images as you want. Could be they are inside the *.odb-file (it's getting bigger and bigger) but no image will be displayed in the form. This bug for big images is a special HSQLDB-bug. I will change the title to show this.
*** Bug 123486 has been marked as a duplicate of this bug. ***
*** Bug 139943 has been marked as a duplicate of this bug. ***
Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug is still the same in Version: 7.6.0.1 (X86_64) / LibreOffice Community Build ID: 776eaf34564cbf3f034a0ba1fd1d5c32ff9ccf1c CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded