Created attachment 133333 [details] 5.4 backtrace Steps: 1) Open attachment 133321 [details] 2) Add data to the various fields 3) Enable Edit > Design Mode and then adjust the various field sizes 4) Disbale Edit > Design Mode and repeat steps 2, 3, 4 5) It will crash sometimes when enabling or disabling design mode Got it to crash with a 5.3 release build, but it didnt fully crash and halted my session by disabling the use of my mouse, so i manually killed the process and when i launched it again, it didnt give me the option to send a crash report. :( Version: 5.4.0.0.alpha1+ Build ID: b82c9439287f58a02a2b42d737fcf110fbfb1244 CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-05-14_01:01:26 Locale: en-US (en_US.UTF-8); Calc: group
Tried multiple cycles, also with gtk2 VCL backend, but could not get it to crash. Arch Linux 64-bit, KDE Plasma 5 Version: 5.5.0.0.alpha0+ Build ID: cee02e81cd3b55fb46eacf5db5713e8bf4363bcd CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on May 19th 2017
Testing with Version: 5.3.3.2 Build ID: 1:5.3.3~rc2-0ubuntu0.16.10.1~lo0 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Layout Engine: new; Locale: ca-ES (ca_ES.UTF-8); Calc: group I got the error: 'object is defunctional' when I resize the forms many times... I'll try to create a video. @Jay, did you get the same error message?
(In reply to Xisco Faulí from comment #2) > I got the error: 'object is defunctional' when I resize the forms many > times... I'll try to create a video. > @Jay, did you get the same error message? Nope no error, just crash.
Created attachment 133439 [details] screencast
Created attachment 133441 [details] object is defunctional backtrace
** 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
Created attachment 142489 [details] gdb bt On pc Debian x86-64 with master sources updated today, I got an assert.
Eike: concerning bt, I "git-searched" sKeyword[eType] and found this old commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=9b419039d9d967ab0d15d1142b27d24851baebeb thought you might have some opinion here.
I doubt that is related to the original problem, which nowhere has some number formatter stuff in the backtrace but loads of accessibility things. This latest "crash" here is an assert() in a debug build (which I'll investigate anyway, apparently an attempt to copy one more character than there are in rStr, which should do no harm in non-debug because that should be the terminating 0-char).
Eike Rathke committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=bfe6e9ecb18e8a3d9da368a1eb48e807ab9041cf Handle English vs locale's General keyword, tdf#33689 follow-up, tdf#107867 It will be available in 6.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.
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-6-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=b75110c87e24d972c98edcb9af91866a41cf1b56&h=libreoffice-6-1 Handle English vs locale's General keyword, tdf#33689 follow-up, tdf#107867 It will be available in 6.1.0.1. 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.
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-6-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=b203abbc50e57105bca654d024b30f7fff129456&h=libreoffice-6-0 Handle English vs locale's General keyword, tdf#33689 follow-up, tdf#107867 It will be available in 6.0.6. 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.
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-6-0-5": http://cgit.freedesktop.org/libreoffice/core/commit/?id=14d7816072104eac67fa9c09915c7803067b7877&h=libreoffice-6-0-5 Handle English vs locale's General keyword, tdf#33689 follow-up, tdf#107867 It will be available in 6.0.5. 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.
Just for info, I don't reproduce the assert. Any update with 6.0.5?
Let's not risk oblivion through NEEDINFO.
@Eike, should it be closed as RESOLVED FIXED instead?
I've done nothing for/against the originally reported crash, just the assert() abortion mentioned in comment 7.
Bug not reproducible in version. Version: 6.3.0.0.alpha0+ (x64) Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55 Locale: zh-TW (zh_TW); UI-Language: en-US Calc: threaded
On pc Debian x86-64 with master sources updated today, I don't reproduce any assert or crash. Any update with a recent LO version?
Created attachment 149839 [details] bt with debug symbols Once I commented, I closed LO and had an assert at this moment.
Created attachment 157442 [details] bt with debug symbols Here's an updated bt on pc Debian x86-64 with master sources updated today.
On pc Debian x86-64 with master sources updated today + non debug build, I don't reproduce this anymore. Anyone to give it a new try with a recent LO version (6.4.3)? A reliable step by step process to reproduce this would be useful to avoid resizing n times.
I guess we should close as Jay is retired and no one else was able to repro.