User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 Build Identifier: LibreOffice 5.1.0.3 The crash appears to be related to the macros I have written in the spreadsheet, such that libreoffice closes itself after having loaded for about 5 seconds, (without pressing anything) I get an "Inadmissible data type. Overflow" error and then if I pick a different job number from the dropdown I get an "unknown SEH error" and libreoffice closes. Reproducible: Always Steps to Reproduce: 1.open spreadsheet and wait about 5 seconds 2.first error appears 3. on the edit form select a different job number. Actual Results: libreoffice crashes. Expected Results: the other job number information should be displayed. [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: yes Reset User Profile?No
Created attachment 124075 [details] a jobsheet spreadsheet, which causes the crashing this file is the test file that demonstrates the issue.
I can confirm crash with Version: 5.2.0.0.alpha0+ and Version: 4.5.0.0.alpha0+; win7 At 4.0 I get the same first error, after change nr. of jobs I get "BASIC runtime error. : Property or method not found: selectedValue.", but LO doesn't crash, regression. Tim, did this macro worked in previous version?
This macro is under development ie. it is not yet complete. before the most recent changes is did not cause a crash of libreoffice calc. (scalc) Changing the job number is supposed to read the values from the main data sheet and put them in the edit form. I was getting an error with a val(somefunctionhere) statement, assumedly because the function returned a null if the cell queried was empty. I changed it to return a blank string instead ("") but for some reason the whole scalc program crashes, so it is rather hard to try and debug. I do have an earlier version from a few days before which does not crash, and doesn't have the changes, but I will need to implement the changes, and I can't see why scalc should crash. it also crashes on linux (slackware) version 4.4.0.3
Created attachment 124225 [details] bt with debug symbols On pc Debian x86-64 with master sources updated today, I could reproduce this. I attached a bt with symbols. I also noticed these logs: warn:legacy.osl:20045:1:xmloff/source/core/xmlerror.cxx:178: An error or a warning has occurred during XML import/export! Error-Id: 0x20040003 Flags: 2 ERROR Class: 4 API Number: 3 Parameters: 0: CharEscapement Exception-Message: UNKNOWN_PROPERTY Position: Public Identifier: System Identifier: file:///home/julien/compile-libreoffice/bugs/99089_jobsheet/jobsheet.ods Row, Column: 2,94886 warn:legacy.osl:20045:1:xmloff/source/core/xmlerror.cxx:178: An error or a warning has occurred during XML import/export! Error-Id: 0x20040003 Flags: 2 ERROR Class: 4 API Number: 3 Parameters: 0: CharEscapementHeight Exception-Message: UNKNOWN_PROPERTY Position: Public Identifier: System Identifier: file:///home/julien/compile-libreoffice/bugs/99089_jobsheet/jobsheet.ods Row, Column: 2,94886 warn:legacy.osl:20045:1:svx/source/svdraw/svdouno.cxx:528: SdrUnoObj::GetUnoControl: This object is not displayed in that particular view! warn:legacy.osl:20045:1:svx/source/accessibility/AccessibleControlShape.cxx:580: AccessibleControlShape::getAccessibleChild: index mismatch! warn:legacy.osl:20045:1:svx/source/accessibility/AccessibleControlShape.cxx:660: AccessibleControlShape::disposing: this should never happen!
I submitted a patch on gerrit here for master sources (future 5.2.0): https://gerrit.libreoffice.org/#/c/23956/
Julien Nabet committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=43109b751bf5fd36318de56b2fb686acc724673f tdf#99089: avoid some crashes in Basic It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
I've tested on the nightly (windows 7 64bit) libo-master~2016-04-11_23.06.26_LibriOfficeDev_5.2.0.0.alpha0_Win_x86.msi and it still crashes as soon as you select a different job from the dropdown list control.
Julien Nabet committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=5304b948781e1f8a1bf5249a260db738e4113079 Related tdf#99089: avoid second crash It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
that second patch seems to have done the job. scalc no longer crashes with this test case. (win 7 64bit) many thanks Julien for the fix. I look forward to it appearing in lo 5.2.0
Thank you Tim for your feedback. Hope the result is still correct too. Don't hesitate to tell me if there's a side effect for some cases. Anyway, I submitted in 1 patch on gerrit a backport on 5.1 branch of the 2 patches, see https://gerrit.libreoffice.org/#/c/23957/ BTW, with my debug build (which gives slower responsiveness from LO), I noticed the parse was quicker with the fix.
And to answer your question, the fix will be on 5.2.0 (that's why it appears as "target" field).
Julien Nabet committed a patch related to this issue. It has been pushed to "libreoffice-5-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=0e19e4e17f5761d071768a11e16eb9d82d792cf4&h=libreoffice-5-1 tdf#99089: avoid some crashes in Basic It will be available in 5.1.3. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
great, glad to see it will come out in 5.1.3 that is less time to wait :-)