Bug 150555 - Crash after resizing Writer's main window
Summary: Crash after resizing Writer's main window
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Przemas
URL:
Whiteboard: target:7.5.0
Keywords:
Depends on:
Blocks: Skia
  Show dependency treegraph
 
Reported: 2022-08-23 00:41 UTC by Przemas
Modified: 2023-12-12 03:14 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
LO logo after bug (80.97 KB, image/png)
2022-08-23 01:02 UTC, Przemas
Details
skia log file with hardware acceleration (151 bytes, text/plain)
2022-08-23 15:53 UTC, Przemas
Details
Windows additional info on program crash (971 bytes, text/plain)
2022-08-23 15:54 UTC, Przemas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Przemas 2022-08-23 00:41:59 UTC
Description:
After multiple resizing of the main window painting is distorted. No letters no icons only random points. After that "show" Writer is sometimes crashed.

Steps to Reproduce:
1.Run Writer
2.Resize window horizontally and vertically several times
3.

Actual Results:
no letters no icons even in menu only non-client (term from Win API) elements exist

Expected Results:
normal rendering client of the window


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 7.4.0.3 (x64) / LibreOffice Community
Build ID: f85e47c08ddd19c015c0114a68350214f7066f5a
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Vulkan; VCL: win
Locale: pl-PL (pl_PL); UI: pl-PL
Calc: CL
Comment 1 Przemas 2022-08-23 01:02:58 UTC
Created attachment 181966 [details]
LO logo after bug
Comment 2 Xisco Faulí 2022-08-23 08:39:59 UTC
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Comment 3 V Stuart Foote 2022-08-23 14:13:10 UTC
With Windows 8.1 os/DE you should probably not be attempting to use Skia Vulkan GPU accelerated rendering. Please post GPU details from the program cache "skia.log"

Found in C:\users\<username>\AppData\Roaming\4\cache folder.

And, then change your render mode to Skia software rendering (aka raster based rendering) done from Tools -> Options -> View  and determine if things improve.
Comment 4 Przemas 2022-08-23 15:49:47 UTC
(In reply to V Stuart Foote from comment #3)
> With Windows 8.1 os/DE you should probably not be attempting to use Skia
> Vulkan GPU accelerated rendering. Please post GPU details from the program
> cache "skia.log"
> 
> Found in C:\users\<username>\AppData\Roaming\4\cache folder.
> 
> And, then change your render mode to Skia software rendering (aka raster
> based rendering) done from Tools -> Options -> View  and determine if things
> improve.

Thank you for response. Guilty is Skia engine. Software rendering works correctly. I attach skia.log and Windows additional info after program crash.
Comment 5 Przemas 2022-08-23 15:53:01 UTC
Created attachment 181980 [details]
skia log file with hardware acceleration
Comment 6 Przemas 2022-08-23 15:54:54 UTC
Created attachment 181981 [details]
Windows additional info on program crash
Comment 7 V Stuart Foote 2022-08-23 16:06:39 UTC
o(In reply to Przemas from comment #5)
> Created attachment 181980 [details]
> skia log file with hardware acceleration

RenderMethod: vulkan
Vendor: 0x10de
Device: 0x128b
API: 1.2.175
Driver: 472.48.0
DeviceType: discrete
DeviceName: NVIDIA GeForce GT 710
Denylisted: no

@Luboš, Julien --the Denylisted "no" suggests we need a tweak to the skia_denylist_vulkan; perhaps add a stanza for Windows 8 and 8.1? Those defunct os are trouble for any brand GPU.
Comment 8 Julien Nabet 2022-08-23 18:49:23 UTC
(In reply to V Stuart Foote from comment #7)
> (In reply to Przemas from comment #5)>
> ...
> @Luboš, Julien --the Denylisted "no" suggests we need a tweak to the
> skia_denylist_vulkan; perhaps add a stanza for Windows 8 and 8.1? Those
> defunct os are trouble for any brand GPU.

I submitted this patch for this:
https://gerrit.libreoffice.org/c/core/+/138743
Comment 9 Commit Notification 2022-08-23 19:31:16 UTC
Julien Nabet committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/e2a16489ff4a65e747e93b28d39096cb259bddd7

tdf#150555: Skia seems to fail with Windows 8/8.1

It will be available in 7.5.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 10 Aron Budea 2022-08-23 23:02:11 UTC
Let's use status FIXED. Thanks, Julien!
Comment 11 Xisco Faulí 2022-08-25 21:19:36 UTC
Hi Przemas,
I'm wondering, do you have the same issue with LibreOffice 7.3.5 ? if so, then denying skia in Windows 8 looks like the right fix, if not, this issue might be related to bug 150236 instead
Comment 12 Przemas 2022-08-26 00:04:40 UTC
(In reply to Xisco Faulí from comment #11)
> Hi Przemas,
> I'm wondering, do you have the same issue with LibreOffice 7.3.5 ? if so,
> then denying skia in Windows 8 looks like the right fix, if not, this issue
> might be related to bug 150236 instead

Hi Xisco, The same issue occurs with LO 7.3.5.2 portable (Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01). It's time to the replacement of Windows...
Comment 13 V Stuart Foote 2022-08-26 00:12:57 UTC
(In reply to Przemas from comment #12)
> Hi Xisco, The same issue occurs with LO 7.3.5.2 portable (Build ID:
> 184fe81b8c8c30d8b5082578aee2fed2ea847c01). It's time to the replacement of
> Windows...

No, just that so long as you are on Windows 8.1, do not try to use Vulkan GPU accelerated rendering.  An upgrade of your operating system to Windows 10 or 11 would not necessarily improve things with Vulkan GPU rendering -- the driver and specific chipset may deliver Vulkan features that are not functional and cause issues.

Skia raster based rendering, or older GDI rendering should otherwise continue to be fully functional.
Comment 14 Xisco Faulí 2022-09-05 13:11:07 UTC
(In reply to Przemas from comment #12)
> (In reply to Xisco Faulí from comment #11)
> > Hi Przemas,
> > I'm wondering, do you have the same issue with LibreOffice 7.3.5 ? if so,
> > then denying skia in Windows 8 looks like the right fix, if not, this issue
> > might be related to bug 150236 instead
> 
> Hi Xisco, The same issue occurs with LO 7.3.5.2 portable (Build ID:
> 184fe81b8c8c30d8b5082578aee2fed2ea847c01). It's time to the replacement of
> Windows...

Thanks for the clarification!!
Comment 15 Commit Notification 2022-09-07 16:04:50 UTC
Xisco Fauli committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/ce79edd7e79c28516ba43814e4f900b2c05ab23a

Revert "tdf#150555: Skia seems to fail with Windows 8/8.1"

It will be available in 7.5.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 16 V Stuart Foote 2022-09-07 16:57:06 UTC
(In reply to Commit Notification from comment #15)
> 
> https://git.libreoffice.org/core/commit/
> ce79edd7e79c28516ba43814e4f900b2c05ab23a
> 
> Revert "tdf#150555: Skia seems to fail with Windows 8/8.1"
> 

@xisco, not sure this is smart. I take cloph and luboš's comments into consideration--but we already deny all Windows 7 use and Windows 8 went EOL long ago. While Windows 8.1 is EOL and dropped hard Jan 2023. [1]

Since Vulkan GPU rendering is very driver dependent, and since the GPU vendors abandon older hardware and older OS as "legacy", we are chasing our tail to allow users on questionable hardware/os combinations to run Vulkan by default.

It is appropriate to broadly deny list Vulkan accelerated rendering as it will reduce the number of BZ issues like this for ill suited hardware/os and driver.

Especially since users so inclined can check on their own if their hardware/os and driver combination is otherwise functional with Vulkan accelerated rendering.

Skia software based raster rendering is stable and usable so we are not eliminating function, rather just preventing headache of excessive BZ churn while we have Vulkan rendering *enabled by default*.

Julien's deny list entries are appropriate.

=-ref-=

[1] https://support.microsoft.com/en-us/windows/windows-8-1-support-will-end-on-january-10-2023-3cfd4cde-f611-496a-8057-923fba401e93#:~:text=Support%20for%20Windows%208.1%20is,no%20longer%20receive%20security%20updates.
Comment 17 Julien Nabet 2023-05-14 07:30:41 UTC
Let's reopen this one since the fix had been reverted.
Comment 18 Julien Nabet 2023-05-14 07:30:49 UTC
Przemas: could you try to upgrade your graphic driver or upgrade Windows since Windows 8/8.1 support (included extended support) is finished and give a new try?
Comment 19 QA Administrators 2023-11-11 03:14:07 UTC Comment hidden (obsolete)
Comment 20 QA Administrators 2023-12-12 03:14:10 UTC
Dear Przemas,

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