Bug 144144 - Crash in: SkiaSalGraphicsImpl::applyXor()
Summary: Crash in: SkiaSalGraphicsImpl::applyXor()
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.0.6.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-28 14:14 UTC by Colin
Modified: 2022-12-27 17:52 UTC (History)
3 users (show)

See Also:
Crash report or crash signature: ["SkiaSalGraphicsImpl::applyXor()"]


Attachments
Composite screen dump of two error panels (242.83 KB, image/png)
2021-08-28 14:14 UTC, Colin
Details
Screen Dump (87.57 KB, image/png)
2022-01-07 10:17 UTC, Colin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Colin 2021-08-28 14:14:23 UTC
Created attachment 174590 [details]
Composite screen dump of two error panels

This bug was filed from the crash reporting server and is br-3551c918-46bf-4498-b1b0-0dba22f5c015.
=========================================
I had been working on a protected sheet and copied some auto filtered rows from sheet 2 to sheet 1. These rows were not contiguous in the source but it was intended to simply append them to the end of the target array.

The date formats were not identical so I changed the 8 copied rows.

I then noticed the previous rows had the incorrect location format and upon trying to change these the application crashed. I did catch a glimpse of a progress bar before it was gone. I have no idea if this was related to the crash reporting or simply the periodic autosave.
 
Restart resulted in the constant flashing of the welcome banner with its message which followed my mouse from monitor to monitor - upper half of the screen image attached. I restarted twice to ensure it was "cleared" 

Next activation of LO recommended recovery of the two open documents which I accepted.

Screen display was odd with a conflict over the positioning of two extensions on the toolbar.

I resolved that by simply closing them.

Attempting to reload Power detective - an extension I have been using for years - resulted in the "discovery" error noted in the lower half of the screen image attached.

The warning is confirmed - nothing exists beyond the cache directory.

The second extension was Style reporter which had only been on my system since Aug 21st - 7 days and only used a couple of times.

I haven't tried to reinstall that.
Comment 1 Roman Kuznetsov 2021-08-28 17:29:15 UTC
If you'll can repeat it with clear steps for reproduction of the problem it would be cool

Can you do some expirements?
Comment 2 Telesto 2021-08-28 17:43:14 UTC
An upgrading 7.1 or even 7.2 might help too..
Comment 3 Colin 2021-08-28 17:45:05 UTC
You have more chance of being struck by lightning TWICE.
It completely screwed my installation.
An update to a later version also failed to remediate.
Completely uninstalling and reinstalling everything exposed another bug -
Even a fresh install of the latest stable release found all the old APPDATA files AFTER uninstallation and Registry flushing with CCleaner.
Now I have to uninstall, find and remove all files on the disk even vaguely resembling LO in program, program data, Appdata and probably even the windows temp folder. Perhaps you could tell me where else to look in case I've missed something. And there I was thinking uninstall meant uninstall.
If these endeavours fail then I can't even use Libre Office - let alone experiment
Comment 4 Colin 2021-08-28 17:47:35 UTC
(In reply to Telesto from comment #2)
> An upgrading 7.1 or even 7.2 might help too..

Been there, done that, p''''d on the stage.

Uninstall doesn't so the complete reinstall just carried the old bug into the new version🤷‍♂️
Comment 5 Telesto 2021-08-28 17:48:08 UTC
(In reply to Colin from comment #3)
> You have more chance of being struck by lightning TWICE.
> It completely screwed my installation.
> An update to a later version also failed to remediate.
> Completely uninstalling and reinstalling everything exposed another bug -
> Even a fresh install of the latest stable release found all the old APPDATA
> files AFTER uninstallation and Registry flushing with CCleaner.
> Now I have to uninstall, find and remove all files on the disk even vaguely
> resembling LO in program, program data, Appdata and probably even the
> windows temp folder. Perhaps you could tell me where else to look in case
> I've missed something. And there I was thinking uninstall meant uninstall.
> If these endeavours fail then I can't even use Libre Office - let alone
> experiment

Launch Libreoffice -> Help -> Restart in safe mode. Restore factory settings -> Whole profile
Comment 6 Colin 2021-08-28 17:58:57 UTC
(In reply to Telesto from comment #5)
> (In reply to Colin from comment #3)
> 
> Launch Libreoffice -> Help -> Restart in safe mode. Restore factory settings
> -> Whole profile

Yay now all I have to do is remember all my old settings and make this version 7.2.0.4 mine.

Thanks. Hopefully, you won't be offended if I don't try to recreate the bug.

I have a nasty suspicion it was associated with the recent installation of Style Reporter which I'm not going to reinstall - even to help you out.

Thanks again - feel free to mark it not a bug - flaky extension or something that will get it off your books.
Comment 7 Colin 2022-01-07 10:17:06 UTC
Created attachment 177369 [details]
Screen Dump

Just discovered something sinister.
After the latest crashing, recovering and reporting I perceived a noisier cooling fan so I investigated.
Attached is the Task Manager Screen.
Libre Office is not running anything. All files closed, I even opened and closed one to try to "flush it out" - Twice. All it does is push the CPU% higher.
Yes, killing the task does kill it
Comment 8 Xisco Faulí 2022-01-27 14:43:42 UTC
According to the crashreport, it's related to SKIA.
Comment 9 Julien Nabet 2022-03-24 16:01:21 UTC
If Skia related (at least for the last crash), this may help:
https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28_Skia_.29
Comment 10 Xisco Faulí 2022-09-08 14:01:36 UTC
According to https://crashreport.libreoffice.org/stats/signature/SkiaSalGraphicsImpl::applyXor(), this issue is no longer reproducible in LibreOffice 7.4.0.3
Please update to the latest version
Closing as RESOLVED WORKSFORME
Comment 11 Colin 2022-09-08 14:14:07 UTC
(In reply to Xisco Faulí from comment #10)
> 
> 
> applyXor(), this issue is no longer reproducible in LibreOffice 7.4.0.3
> Please update to the latest version
> Closing as RESOLVED WORKSFORME

And when does 7.4 reach the safe community release?
Comment 12 Xisco Faulí 2022-09-08 14:16:31 UTC
(In reply to Colin from comment #11)
> (In reply to Xisco Faulí from comment #10)
> > 
> > 
> > applyXor(), this issue is no longer reproducible in LibreOffice 7.4.0.3
> > Please update to the latest version
> > Closing as RESOLVED WORKSFORME
> 
> And when does 7.4 reach the safe community release?

I believe you mean 'still' phase ? around 7.4.4