Created attachment 186870 [details] Lorem ipsum file that causes a crash The attached document causes a trash when I do the following: 1- Select the Quotations paragraph format using the navigator 2- Right-click -> Modify 3- Select Area 4- Click None 5- Watch it go down in a blaze of glory I saw the crash with 7.5.0.3. I updated to 7.5.2.2 and I still see it.
Tested with OpenSUSE 15.4 64bit rpm Linux Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded Doesn't see any buggy behavior when setting Area → None. Might be a special Windows Bug. Did you reset you user profile for LO? Did you try it with Help → Restart in Safe mode? What is chosen in Tolls → LibreOffice → View → Skia?
Could you apply https://wiki.documentfoundation.org/QA/FirstSteps ?
Did you reset you user profile for LO? No. Did you try it with Help → Restart in Safe mode? Yes. I tried with no extensions and it crashes. I tried using the default factory settings option and it crashes also, although it takes more time to do so than in normal mode. On restart, I don't get the option to send a crash report. What is chosen in Tolls → LibreOffice → View → Skia? Everything is chosen
(In reply to L Duperval from comment #3) > Did you reset you user profile for LO? > > No. > > Did you try it with Help → Restart in Safe mode? > > Yes. I tried with no extensions and it crashes. I tried using the default > factory settings option and it crashes also, although it takes more time to > do so than in normal mode. > > On restart, I don't get the option to send a crash report. > > What is chosen in Tolls → LibreOffice → View → Skia? > > Everything is chosen You can try to reset your user profile: Help - Restart in Safe Mode - Restart - Reset to factory settings - check both options and click Apply and Restart. Then, retest to see if you can reproduce the bug you reported.
That's what I did for the factory settings. Sorry if it wasn't clear from my explanation. I'll have to see about retrying without a profile. Is there a way to force the sending of a crash report when Writer crashes or when I restart? I found a workaround by editing the ODT file and removing the Area styles in the styles.xml file but that's hardly a solution. :) L
[Automated Action] NeedInfo-To-Unconfirmed
I just realized that the problem appears when you click on something that isn't None to something else. So for example, if I take the Text Body Style From the Area tab with None selected Click Color: No crash Click Gradient: crash From the Area tab with None selected Click Gradient: No crash Click Image: Crash From the Area tab with None selected Click Image: No crash Click Gradient: Crash So there's something in the process of clicking away from a selected button that's different with the None button that allows me to click on another button with no problem. But clicking away from any other button makes things crash. Hopefully that helps identify the problem.
No crash in Version: 7.5.3.1 (X86_64) / LibreOffice Community Build ID: d29ee673721b12c92b3de9b9663473211414f0db CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ro-RO (ro_RO); UI: en-US Calc: threaded
I can't see it either on Ubuntu 20.04 with LO 7.5.3.2. L Duperval, any chance you could provide a backtrace with WinDbg by following these steps? https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Created attachment 187217 [details] backtrace
I uploaded the backtrace file. I also had a crash while using Draw and trying to change the background. So I tried with Calc, and lo and behold, changing the background there cause a crash also.
Upgraded to 7.3.5.2 on Windows and I still get the crash
(In reply to L Duperval from comment #7) > I just realized that the problem appears when you click on something that > isn't None to something else. So for example, if I take the Text Body Style > > From the Area tab with None selected > > Click Color: No crash > Click Gradient: crash Not reproduced. We still don't have this info from you: copy and paste here the contents of your Help - About by clicking the copy button. This allows us to know more about your system. I'm particularly interested in if it crashes when you have Skia activated. The backtrace doesn't have symbols. You could try Win-x86@39 from https://dev-builds.libreoffice.org/daily/master/current.html Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 22950a9b008e1bb22fa9e54b5d45715e25fee764 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded
Created attachment 187337 [details] Help About
(In reply to L Duperval from comment #14) > Created attachment 187337 [details] > Help About That's a screenshot while we asked you to click the button to copy the text. We can see that you are using Skia/Raster, which should be more stable than Vulkan that uses the graphics processing unit.
https://vento.so/view/a018e762-1594-4080-962b-b97a4a8e41bd Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
The above happens on a page but is similar to the bug I reported originally.
Thank you for the video. Let's see if someone with Skia/Vulkan can confirm.
I can't reproduce with Version: 7.5.7.1 (X86_64) / LibreOffice Community Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded neither Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Maybe updating the video card driver from the vendor could help.
L Duperval, can you please test version 24.2 and see if it is resolved? If not available at the top of the page, it would be in the pre-releases at the bottom: https://www.libreoffice.org/download/download/ Asking because others have reported a similar issue fixed in that version, see bug 154091 and bug 157203.
I'm on 7.6.6.1 on Windows 11 on a new machine and I get the same problem. I installed 24.2 but had to remove it because the performance was so bad (bug 160508)
I'm unable to reproduce the same behavior in Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded or Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded I'm not sure if this is important or not, but the latter version I listed had significantly more lag when I was scrolling through the file.
L Duperval: seeing Armondo's last comment, it seems relevant regarding your comment 21 about performance. You could try with a daily build, Win-x86_64@tb77-TDF from https://dev-builds.libreoffice.org/daily/master/current.html It installs separately.
Regarding the Area fill crash, others have reported that they don't see the issue in 24.2.2+. Would be great if you could test the latest 24.2 release.
Dear L Duperval, 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 L Duperval, 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