Currently with Version: 6.0.5.2 (x64) Build-ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group I have very many crashes, AFAIR mostly Writer, for example modifying Variable Fields. Currently no way to make it 100% reproducible known. Related Crash reports: http://crashreport.libreoffice.org/stats/crash_details/059f963f-9560-4035-84e9-e518ff5e3033 http://crashreport.libreoffice.org/stats/crash_details/3c8ab53a-6285-4838-9843-3e471ca00da7 http://crashreport.libreoffice.org/stats/crash_details/37a31a0e-8685-4374-b409-25f4a9ae1eb1 http://crashreport.libreoffice.org/stats/crash_details/fb4cda37-f713-4440-aa68-ab8f1a94dff2 (and others)
Additional info: a) Modifying Variable fields the CRASH always came in the moment when I clicked [OK] after having modified
Could you please create and attach a screencast showing the steps? There are various free screencast software available for use, including Camstudio (Windows), Jing (Mac), Simple Screen Recorder (Linux) or screencast-o-matic.com (Web).
@Telesto, @Kompi, Would you like you try if you can reproduce this crash? according to the trace, I would say it's happening when an item is deleted from the insert field dialog...
I need steps to repro. Operations with "variable" fields work fine for me
Is the issue specific for the 6.0 branche? Or also in 6.1?
(In reply to Xisco Faulí from comment #3) > Currently no way to make it 100% reproducible Steps will follow as soon as I know them
anyway, it would be nice if you could give us more information to narrow it down...
putting to NEEDINFO until more info is provided...
crashreport.libreoffice.org/stats/crash_details/66d4be52-d70b-403e-9373-c7ec271d7d6c Any hints from the crash reports? Currently I only can say that it seems that the crash happens when I am editing large documents with much linked contents.
Crash reports go back to 5.2 (introduction of the crash reporter); rather old bug I guess. I'm noticing timer/solar mutex in the trace. So might be non-thread safe process. LibO might be still updating a treelist of all Variable fields when pressing OK (or something like that). Because of a long list or because lots of CPU load. However, this is pure speculation from my side (not a DEV). I'm mostly wrong ;-) It's possible that this happens more often (without being the root cause), because of author Jan-Marek Glogowski <glogow@fbihome.de> 2017-08-28 19:58:32 +0200 committer Jan-Marek Glogowski <glogow@fbihome.de> 2017-09-26 09:42:11 +0200 commit 4baec725e0dc0713f0d47003e9b10bc3b62f56ff (patch) tree 72f21c28416068e46133964e420ca094af8b7587 parent f633dcdfc0ad7a13d096d97b6753b55e8f8a3f07 (diff) WIN run main thread redirects ignoring SolarMutex -> See also bug 118786. LibO5.4. should crash less often in that case.
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-20190321
Dear Rainer Bielefeld Retired, 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