Problem description: During editing Writer document LibO crashes
* mostly with an error message "Bad Allocation" or "osl::Thread::create failed", sometimes without message.
Very annoying, happens more than 1 times per day
Steps to reproduce:
no way known how to make that reproducible
Operating System: Windows 7
Version: 220.127.116.11 release
If you are not able to find the steps to reproduce, I strongly recommend you provide a test document. Otherwise we can not find the problem and this can not be fixed.
I set this to needinfo. Please set it back to UNCONFIRMED once you have provided the test file or furthet info. Thanks.
I doubt that it will be possible to submit "a" test document. Current state of knowledge is that the crash can happen more or less with any document if you only work long enough with several documents opened, switching focus, copy from one to an other, simply what will be done during busy working. I also can't find out what kind of edit causes the crash.
May be it will be possible to find some preconditions (auto spell check or whatever).
At least the "bad allocation" crash also appears in Calc, I saw it while exporting a Spreadsheet on a ftp://location to a ftp location. I am still trying to find out conditions how to make those crashes reproducible.
Created attachment 103643 [details]
Typical error message, no problem for several days, today 3 crashes in 2 documents.
Things became much worse after update to Version: 18.104.22.168 Build-ID: 62ad5818884a2fc2e5780dd45466868d41009ec0.
Suspect: related to the User Profile. With a new profile I did not observe the crashes, but still some more tests are necessary.
I have some first reproducible results:
I can reproduce the problem with a particular document with a newly created document. A symptom is quick rising memory consumption shortly before the crash by simply typing a character on and on. Unfortunately I can not publish the document, but now I have a chance to find a similar document without confidential contents.
This will take some time, I currently do not use LibreOffice Writer for normal work because of those crashes.
(In reply to comment #6)
The observed problem now is Bug 83476, has nothing to do with this one.
Backtrace of a crash could help: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
You can also change this to RESOLVED WORKSFORME, if the problem went away.
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 INVALID
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
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!
This NEEDINFO Message was generated on: 2015-06-08
My reply to Comment 7 see in Bug 57999c20
The bug still exists for Version: 22.214.171.124.0+
Build-ID: 24c5f9979e61fde7b098af60756a4890e5713390 Gebietsschema: de_DE
After more or less 10 crashes today I again terminate my annual LibO test and switch back to AOO, what has much less features (<http://cor4office.blogspot.de/2015/06/looking-back-and-forth.html>), but allows me to work with it - what also is a nice feature.
That Backtrace proceeding seems to too expensive to me - see you again June 2016
(In reply to Bugcruncher from comment #10)
> My reply to Comment 7 see in Bug 57999c20
> The bug still exists for Version: 126.96.36.199.0+
> Build-ID: 24c5f9979e61fde7b098af60756a4890e5713390 Gebietsschema: de_DE
> After more or less 10 crashes today I again terminate my annual LibO test
> and switch back to AOO, what has much less features
> (<http://cor4office.blogspot.de/2015/06/looking-back-and-forth.html>), but
> allows me to work with it - what also is a nice feature.
> That Backtrace proceeding seems to too expensive to me - see you again June
Backtrace price = $0
Obviously there is something special in your system as 10 crashes per day is not "business as usual" in LibreOffice land.
I will leave this as NEEDINFO, while we wait for a backtrace or reproducible steps.
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID 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 FDO
Message generated on: 2015-07-18