Description: Deleting a big amount of sheets (from 40 up to 99) without saving the file, LibreOffice crashes with a bad allocation error Steps to Reproduce: 1. Open the provided dummy file (is a worksheet with 100 empty sheets) 2. Delete the sheets (from 40 up to 99) without saving Actual Results: LibreOffice crashes with a bad allocation dialog error Expected Results: LibreOffice works Reproducible: Always User Profile Reset: Yes Additional Info: works fine with: Versione 3.6.7.2 (Build ID: e183d5b) crash: Versione: 4.4.5.2 Build ID: a22f674fd25a3b6f45bdebf25400ed2adff0ff99 Versione locale: it_IT Versione: 5.0.1.2 Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Versione locale: it-IT (it_IT) Versione: 5.0.5.2 Build ID: 55b006a02d247b5f7215fc6ea0fde844b30035b3 Versione locale: it-IT (it_IT) Versione: 5.1.5.2 Build ID: 7a864d8825610a8c07cfc3bc01dd4fce6a9447e5 Thread CPU: 4; Versione SO: Windows 6.1; Resa interfaccia: predefinito; Versione locale: it-IT (it_IT); Calc: group Versione: 5.1.6.2 Build ID: 07ac168c60a517dba0f0d7bc7540f5afa45f0909 Thread CPU: 4; Versione SO: Windows 6.1; Resa interfaccia: predefinito; Versione locale: it-IT (it_IT); Calc: group Versione: 5.1.6.2 Build ID: 07ac168c60a517dba0f0d7bc7540f5afa45f0909 Thread CPU: 4; Versione SO: Windows 6.1; Resa interfaccia: predefinito; Versione locale: it-IT (it_IT); Calc: group Version: 5.2.4.2 Build ID: 3d5603e1122f0f102b62521720ab13a38a4e0eb0 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Locale: vec-IT (it_IT); Calc: group Versione: 5.3.0.0.beta2 Build ID: a7e30712ad6d8bc9286007b37aa581983e0caba3 Thread CPU: 4; Versione SO: Windows 6.1; Resa interfaccia: predefinito; Layout Engine: new; Versione locale: it-IT (it_IT); Calc: group User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Created attachment 130153 [details] test file test file to play with
in some cases, if you have removed 99 sheets you can reproduce the issue trying to close the document without saving. In this specific case the error is related to mergedlo.dll
Created attachment 130155 [details] windows crash report report files created by windows
Hi Marina, I don't reproduce with LO 4.4.5.2 Build ID: a22f674fd25a3b6f45bdebf25400ed2adff0ff99 Locale : fr_FR and Windows 7 Home. Selecting "Close" after deleting, has displayed the save proposal. Jacques
No repro with: Version: 5.4.0.0.alpha0+ Build ID: 215cbfb460326010737433c2020638e9388a88a4 CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2017-01-02_23:58:32 Locale: nl-NL (nl_NL); Calc: CL
No repro. Marina: do all the crashes happen with a 32-bit LibreOffice? Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: 1a58cdf8af1aba52ce0a376666dd7d742234d7cf CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on January 4th 2016
(In reply to Buovjaga from comment #6) > No repro. > > Marina: do all the crashes happen with a 32-bit LibreOffice? yep
I can't reproduce it in Versión: 5.3.2.2 Id. de compilación: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1 Subproc. CPU: 1; SO: Windows 6.1; Repr. de IU: predet.; Motor de trazado: HarfBuzz; Configuración regional: es-ES (es_ES); Calc: group
No repro with: Version: 5.5.0.0.alpha0+ Build ID: 076ed447f694239d5c67adee528ea6e471d909ff CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-06-09_23:54:20 Locale: nl-NL (nl_NL); Calc: CL @Marina Does 5.4.0.0.beta2 also crash?
(In reply to Telesto from comment #9) > No repro with: > Version: 5.5.0.0.alpha0+ > Build ID: 076ed447f694239d5c67adee528ea6e471d909ff > CPU threads: 4; OS: Windows 6.19; UI render: default; > TinderBox: Win-x86@42, Branch:master, Time: 2017-06-09_23:54:20 > Locale: nl-NL (nl_NL); Calc: CL > > @Marina > Does 5.4.0.0.beta2 also crash? repro with: Version: 6.0.0.0.alpha0+ Build ID: c50ae538a6656889c68c43bd9fe0347c61c82aa5 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-06-18_23:58:50 Locale: it-IT (it_IT); Calc: group
Does this happen, if you set the undo steps to a small value in Tools - Options - LibO - Advanced - Expert config: org.openoffice.Office.Common/Undo ?
(In reply to Buovjaga from comment #11) > Does this happen, if you set the undo steps to a small value in Tools - > Options - LibO - Advanced - Expert config: org.openoffice.Office.Common/Undo > ? changed the value from 100 to 1. current behaviour: 1) removed 99 sheets 2) File -> Close 3) select "close without save" works fine without crash or errors. Versione: 5.4.0.1 Build ID: 40m0(Build:1) CPU threads: 4; OS: Linux 4.11; UI render: predefinito; VCL: gtk3; Versione locale: it-IT (it_IT.UTF-8); Calc: group
A duplicate of Bug 67525?
@Marina, Could you pleae try to get a backtrace as explained here: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg ?
(In reply to Marina Latini from comment #12) I see that your original bug report was reproduced in Windows. However, in Comment 12 you said if you set the undo step to 1, there is no crash, but this is done in linux. Does this mean that you can also reproduce the bug in Linux if the undo steps is 100?
Also could you please specify your RAM size. In the past I do encounter some bad allocation error in low memory machines.
(In reply to Kevin Suo from comment #16) > Also could you please specify your RAM size. In the past I do encounter some > bad allocation error in low memory machines. Hi Marina, Could you please answer this question an the one in comment 15 ?
Not reproduce バージョン: 6.0.1.1 (x64) Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 CPU threads: 2; OS:Windows 6.1; UI render: default; ロケール: ja-JP (ja_JP); Calc: group
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20181203
Repro with: Version: 6.2.0.1 Build ID: 0412ee99e862f384c1106d0841a950c4cfaa9df1 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded Note: remove the sheets one by one.
(In reply to Marina Latini (CIB) from comment #20) > Repro with: > Version: 6.2.0.1 > Build ID: 0412ee99e862f384c1106d0841a950c4cfaa9df1 > CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; > Locale: en-US (en_US); UI-Language: en-US > Calc: threaded > > Note: remove the sheets one by one. The NEEDINFO was for: (In reply to Kevin Suo from comment #16) > Also could you please specify your RAM size. In the past I do encounter some > bad allocation error in low memory machines. and (In reply to Kevin Suo from comment #15) > (In reply to Marina Latini from comment #12) > I see that your original bug report was reproduced in Windows. However, in > Comment 12 you said if you set the undo step to 1, there is no crash, but > this is done in linux. > > Does this mean that you can also reproduce the bug in Linux if the undo > steps is 100?
grouping cell button error in version 6.2 combining cells in a table with a standard panel works well when the tab bar then the merge button works to unite the cells and no longer separates the cells.
Hi Marina, This issue was reported on 2017-01-04 and you are the only one who can reproduce it... I'm wondering if it's a problem with your PC rather than a LibreOffice problem...
Mine works also! welcome Castro B, http://internetvergelijken.nl
(In reply to Xisco Faulí from comment #23) > Hi Marina, > This issue was reported on 2017-01-04 and you are the only one who can > reproduce it... > I'm wondering if it's a problem with your PC rather than a LibreOffice > problem... setting to NEEDINFO
Dear Marina Latini (CIB), This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Marina Latini (CIB), Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. 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 (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) 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. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp