Description: After a crash. I load my files. Clean pages are inserted everywhere. When I try to correct this mistake, there is a new crash... So I can't correct. Actual Results: Files not correct Expected Results: Nothing happened. The files seemed to be unchanged Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: fr Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no
Too long to have good files
If I well understood, this happens only with specific files? I mean, if you do this: - launch Writer to create a brand new file - type "test" - save the file - close LO - reopen the file no crash? Without file attached to try to reproduce, it's impossible to investigate. Since you can't sanitize the files because of this problem, we're a bit stuck. So I hope there's nothing confidential/private part in these files so you can attach one of them.
high power consumption. memory at 87%. crash in a few minutes without working.
(In reply to Gérard DUBOIS from comment #3) > high power consumption. memory at 87%. crash in a few minutes without > working. Do you mean with brand new file + step by step mechanism provided in my previous comment or only with specific files? If only specific files, could you "sanitize" them by using https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission ?
good evening Only heavy files may libreoffice to crash, but when I look to Microsoft tasks, I clearly see that Libreoffice works with 29% of processor and all other tasks only 2%, Memory is higher than 1 Go and high power consumption is only for LibreOffice. This appears for one heavy file or another, no matter. I have intel 5 core, 8 Go memory, 450 Watts power, windows 10. Thank you.
(In reply to Gérard DUBOIS from comment #5) > good evening Hmm, doesn't sound right. Any change to share an example file? Would be really helpful. Thanks in advance
Dear Gérard DUBOIS, 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 Gérard DUBOIS, 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