Created attachment 121158 [details] the file with the dialog that causes the error I'm developing a base file with embedded firebird databese connected also via macro to an externale firebird dB. I'm designing an dialog named DLG_reteRisc with a lot of object. When I save the file I obtainSEH Exception: ACCESS VIOLATION, than libre office crash down. The file recovery work fine: in fact I havan't lost my changes, but when I open the dialog to modify it I get the same error. I'm sorry for my english. Thank you for the hel
I see no crash on OSX 10.11.1 with LO 5032 I can load the dialog DLG_reteRisc in the macro editor and no crash occurs. Windows specific
@Alberto : you indicated in your report that this is x86 Windows - which version of Windows are you running, and are you sure that you're running a 32bit x86 version of LibreOffice ?
(In reply to Alex Thurgood from comment #2) > @Alberto : you indicated in your report that this is x86 Windows - which > version of Windows are you running, and are you sure that you're running a > 32bit x86 version of LibreOffice ? I'm working with a win10 home (64bit) and I'm working with libreoffice 32bit (Version: 5.0.3.2 Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Versione locale: it-IT (it_IT)) P.S. I'm still using libreoffice 32bit because I've tried the 64bit version on another PC and I wasn't able to activate embedded firebird with libreoffice 64bit version (even if I've activated the use of experimental features)
Thanks Alberto - yes, embedded firebird was disabled from build for 64bit Windows version of LibreOffice, and as far as I know, hasn't been re-enabled. We need a Windows QAer to check this one out though. In the past, there have been other reports about SEH Access violations when using Base on Windows, perhaps your case is related.
I can confirm crash with 5.0.3.2 (x64), win7. Edit dialog DLG_reteRisc, save. No crash. Close LO via right upper X button -> crash No crash with Version: 5.2.0.0.alpha0+ (x64) Build ID: e7c78e67292ad93c6a4a0772d8b06a0e6e7d26c8 Threads 1; Ver: Windows 6.1; Render: default; TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-11-30_22:37:14 Alberto, please could you test with dev version? http://dev-builds.libreoffice.org/daily/master/ Thank you
(In reply to raal from comment #5) > I can confirm crash with 5.0.3.2 (x64), win7. Edit dialog DLG_reteRisc, > save. No crash. Close LO via right upper X button -> crash > > No crash with Version: 5.2.0.0.alpha0+ (x64) > Build ID: e7c78e67292ad93c6a4a0772d8b06a0e6e7d26c8 > Threads 1; Ver: Windows 6.1; Render: default; > TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-11-30_22:37:14 > > Alberto, please could you test with dev version? > http://dev-builds.libreoffice.org/daily/master/ > Thank you I can confirm that the file doesn't crash using Version: 5.2.0.0.alpha0+ (x64) Build ID: e7c78e67292ad93c6a4a0772d8b06a0e6e7d26c8 Threads 4; Ver: Windows 6.19; Render: GL; TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-11-30_22:37:14 Locale: it-IT (it_IT) thank you
It could be interesting to give a try to a 5.1.0 daily build, seehttp://dev-builds.libreoffice.org/daily/libreoffice-5-1/ Indeed, 5.1.0 should be available in February 2016 according to https://wiki.documentfoundation.org/ReleasePlan. But in this same page, there's not even 5.2.0 date (even if I suppose about 6 months later if LO keeps the same pace of releases).
(In reply to Julien Nabet from comment #7) > It could be interesting to give a try to a 5.1.0 daily build, > seehttp://dev-builds.libreoffice.org/daily/libreoffice-5-1/ > > Indeed, 5.1.0 should be available in February 2016 according to > https://wiki.documentfoundation.org/ReleasePlan. But in this same page, > there's not even 5.2.0 date (even if I suppose about 6 months later if LO > keeps the same pace of releases). Also with libreoffice 5.1.0 Version: 5.1.0.0.beta2+ Build ID: afa8fec8367c747cbf50d81fe836dd1679b85867 Threads 4; Ver: Windows 6.2; Render: GL; TinderBox: Win-x86@62-merge-TDF, Branch:libreoffice-5-1, Time: 2015-12-09_23:10:03 Locale: it-IT (it_IT) it seems work correctly without any crash. Thank you a lot. Alberto