Bug 157203 - CRASH when reset drawing object area fill to NONE
Summary: CRASH when reset drawing object area fill to NONE
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.6.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: high critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: possibleRegression, wantBacktrace
: 157749 159367 159391 160453 (view as bug list)
Depends on:
Blocks: Area-Fill-Tab Crash
  Show dependency treegraph
 
Reported: 2023-09-12 09:49 UTC by Rainer Bielefeld Retired
Modified: 2024-04-03 22:14 UTC (History)
8 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample Document (10.86 KB, application/vnd.oasis.opendocument.graphics)
2023-09-12 09:49 UTC, Rainer Bielefeld Retired
Details
this document in 24.2.0.2 is working, as NOT in 7.6 (142.36 KB, application/vnd.oasis.opendocument.text)
2024-01-28 18:16 UTC, loic_dupont
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Bielefeld Retired 2023-09-12 09:49:20 UTC
Created attachment 189510 [details]
Sample Document

Steps how to reproduce with  Installation of Version: 7.6.1.1 (X86_64) 
Build ID: c7cda394c5de06de37d8109c310df89a4d4c3a98
CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: Locale: de-DE (de_DE); UI: de-DE; Theme: Elementary
Calc: CL threaded – Normal User Profile :

1. Open attached sample document
2. Click drawing (containing Text "BSK 3.7"
   » becomes selected
3. ˋRightclick → Area → Click [None]ˊ 
   » Expected: Background Color vanishes
    Actual: Crash                                 😥

Additional Info 
----------------
a) Crash does not happen with newly created user profile. So might be related to
   Add-Ons, damages in User Profile, something else. 
   Some more reseearch required.

b) no crash report! 

c) in duump.ini I see:
ProductName=LibreOffice
Version=7.6.1.1
BuildID=c7cda394c5de06de37d8109c310df89a4d4c3a98
URL=https://crashreport.libreoffice.org/submit/
UseSkia=false
Language=de-DE
CPUModelName=AMD Ryzen 5 3600 6-Core Processor              
CPUFlags=sse3 pclmulqdq monitor ssse3 fma cpmxch16b sse41 sse42 movbe popcnt aes xsave osxsave avx f16c rdrand msr cx8 sep cmov clfsh mmx fxsr sse sse2 ht fsgsbase bmi1 avx2 bmi2 rdseed adx sha lahf abm sse4a syscall mmxext rdtscp
MemoryTotal=16726912 kB
Comment 1 Xisco Faulí 2023-09-12 10:14:19 UTC
No crash with

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 13de5fc5396db63d4bd2f3e5fb4dc66c7ddd601f
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: x11
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded
Comment 2 Xisco Faulí 2023-09-12 10:16:31 UTC
no crash in

Version: 7.6.0.3 (X86_64) / LibreOffice Community
Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265
CPU threads: 1; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

either
Comment 3 Rainer Bielefeld Retired 2023-09-12 10:37:35 UTC
Is version from original report "Master"? I don't understand the picker.

a1) Also Safe Mode heals the crash problem

I will try to find out whether a Add-on or similar is the root of the problem.

Butt also can be some very special (graphics?) setting?
Comment 4 Stéphane Guillou (stragu) 2023-09-12 13:22:34 UTC
(In reply to Rainer Bielefeld Retired from comment #3)
> Is version from original report "Master"? I don't understand the picker.

We haven't added the version 7.6.1 just yet because we're still at the pre-release stage. But I guess we could add and rename later, I'll do that now.

(In reply to Rainer Bielefeld Retired from comment #0)
> 1. Open attached sample document
> 2. Click drawing (containing Text "BSK 3.7"
>    » becomes selected
> 3. ˋRightclick → Area → Click [None]ˊ 
>    » Expected: Background Color vanishes
>     Actual: Crash                                 😥

No repro either with:

Version: 7.6.1.1 (X86_64) / LibreOffice Community
Build ID: c7cda394c5de06de37d8109c310df89a4d4c3a98
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Let us know what you find out about your configuration. Thank you!
Comment 5 Stéphane Guillou (stragu) 2023-10-16 11:39:33 UTC
*** Bug 157749 has been marked as a duplicate of this bug. ***
Comment 6 Stéphane Guillou (stragu) 2023-10-16 11:41:23 UTC
Confirmed via duplicate.
Comment 7 Stéphane Guillou (stragu) 2023-10-16 11:53:13 UTC
Rainer and MadLadDesigns: were you both using the tabbed user interface? If so, does it make a different if you use the classic toolbar interface instead?
Comment 8 MadLadDesigns@gmail.com 2023-10-16 23:32:31 UTC
Yes, it was through the tabbed user interface. It's fine through the standard toolbar.
Comment 9 Stéphane Guillou (stragu) 2023-10-17 15:04:27 UTC
If possible at all, please collect and attach a backtrace: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Comment 10 Stéphane Guillou (stragu) 2024-01-25 03:52:08 UTC
*** Bug 159367 has been marked as a duplicate of this bug. ***
Comment 11 Buovjaga 2024-01-25 06:40:39 UTC
With Tabbed interface, I can't reproduce with 7.6.4 or master on Windows.

To all affected by this: download Win-x86@39 from https://dev-builds.libreoffice.org/daily/master/current.html and install it (it installs separately and won't mess with your stable version).

Try to reproduce the crash. If you get the crash, follow this procedure: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

Remember to include this step when setting up WinDbg:

Alternatively if you wish to also debug both the standard build and master build (Win-x86@39 tinderbox), paste the following instead

CACHE*C:\symbols;SRV*https://dev-builds.libreoffice.org/daily/master/Win-x86@39/symbols;SRV*https://dev-downloads.libreoffice.org/symstore/symbols;SRV*https://msdl.microsoft.com/download/symbols
Comment 12 Buovjaga 2024-01-25 06:41:37 UTC
Also, if possible, get the Windows 7.6 bibisect repository and perform a bibisect to find out when the crash was introduced.

https://wiki.documentfoundation.org/QA/Bibisect
https://wiki.documentfoundation.org/QA/Bibisect/Windows
Comment 13 Xisco Faulí 2024-01-26 19:07:17 UTC
*** Bug 159391 has been marked as a duplicate of this bug. ***
Comment 14 roger 2024-01-27 11:06:13 UTC
I have confirmed that this bug also exists in Draw, including Safe Mode.
Comment 15 Buovjaga 2024-01-27 11:21:23 UTC
(In reply to roger from comment #14)
> I have confirmed that this bug also exists in Draw, including Safe Mode.

If you want to help track the issue down, please see comment 11 and 12.
Comment 16 roger 2024-01-27 12:16:21 UTC
I have installed Win-x86@39 (Version: 24.8.0.0.alpha0+ (x86) / LibreOffice Community
Build ID: ce53519f025158f8f64a4e8603c8c6e0dc35473a
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-GB (en_GB); UI: en-US
Calc: threaded)

The bug did not occur - Shape/area behaved as expected.
Comment 17 Stéphane Guillou (stragu) 2024-01-27 23:35:46 UTC
Thanks Roger.

Can you (or someone else who reproduces in 7.6) also test the soon-to-be-released 24.2 version?

Given that some can reproduce with safe mode, I'll remove the bits about the tabbed interface
Comment 18 loic_dupont 2024-01-28 18:14:52 UTC
Greetings, everyone ! 

Confirming that switching to 

Version: 24.2.0.2 (X86_64) / LibreOffice Community
Build ID: b1fd3a6f0759c6f806568e15c957f97194bbec8f
CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: fr-FR (fr_FR); UI: en-US
Calc: CL threaded

This is WORKING AS EXPECTED, we can switch on and off area filling either by properties windows and by rubban buttons.
Comment 19 loic_dupont 2024-01-28 18:16:08 UTC
Created attachment 192206 [details]
this document in 24.2.0.2 is working, as NOT in 7.6
Comment 20 loic_dupont 2024-01-28 18:19:09 UTC
And, to be fully identical except version, switched back to french too, and neither NO MORE crashing in FRENCH UI.
Comment 21 Stéphane Guillou (stragu) 2024-01-29 02:31:14 UTC
Looks like the same mysterious crash as bug 154091, which is also "works for me" in 24.2.

Would be wonderful if someone who can reproduce consistently could bibisect the cause and/or the fix.
We know 7.6.4 crash. If the upcoming 7.6.5 doesn't, it'll be easier to pinpoint the fix.

https://wiki.documentfoundation.org/QA/Bibisect
Comment 22 Xisco Faulí 2024-01-29 09:58:11 UTC
For those who can reproduce the crash, is it possible to test with a libreoffice-7-6 daily build from https://dev-builds.libreoffice.org/daily/libreoffice-7-6/? I'm thinking it might be related to https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7-6&id=6a0d4247b73d16d7e70ab146aadfbed75721f8bd
Comment 23 Matt K 2024-02-03 23:58:11 UTC
No crash with following daily build:

Version: 7.6.5.0.0+ (X86_64) / LibreOffice Community
Build ID: 13c748e7998b6df02e23815f337e9ab4d04172f3
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 24 Stéphane Guillou (stragu) 2024-04-02 02:48:04 UTC
Another user reproduces in 7.6.6 in Calc: bug 160453.
Comment 25 Matt K 2024-04-02 22:25:14 UTC
No repro with following daily build:

Version: 7.6.7.0.0+ (X86_64) / LibreOffice Community
Build ID: d6d502f41346b021d369c27c9ed969d75d680986
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 26 Stéphane Guillou (stragu) 2024-04-03 22:09:50 UTC
*** Bug 160453 has been marked as a duplicate of this bug. ***
Comment 27 Stéphane Guillou (stragu) 2024-04-03 22:14:36 UTC
Matt, I understand you never reproduce this crash, even in earlier versions?
There is something inconsistent, some testers say it only happens with the tabbed UI, others can reproduce with the toolbars.

Bug 160453 reporter also says it is fixed in 24.2, as in comment 18, so let's mark as "works for me". Other users affected: please double-check that it is indeed fixed for you in 24.2. If not, please provide precise steps again.

If anyone can give it a go, a bibisect for the cause and/or the fix would still be really appreciated: https://bibisect.libreoffice.org/