Bug 151564 - Crash for nebulous reason possibly involving scrolling when low available memory
Summary: Crash for nebulous reason possibly involving scrolling when low available memory
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.6.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-16 12:17 UTC by Steve Lawson
Modified: 2023-02-22 12:11 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Lawson 2022-10-16 12:17:42 UTC
Description:
Over the last few releases, Writer [and, now also Calc] has been VERY unstable.  It mostly crashes when I'm scrolling a document.  In particular a book I wrote using Writer that is 466 pages long [119,578 words, 688,145 characters], has numerous images, and footnotes, and many custom styles]
Over time, I've attempted to characterize this issue, but have failed.
I thought it was only happening when I attempt edits in my book [I can usually only manage a couple before it crashes, though not concurrently running memory hog programs like Firefox, seems to improve my edit time].  BUT, I purchased an O2Ring PulseOx sensor, and loaded the overnight data it collected, for the first time, as CSV opened in Calc, and scrolling through it triggers a crash--repeatedly.  And, when these crashes occur, ALL open LibreOffice documents vanish!  The CSV is 194,464 characters -- mostly numbers.

I tried to come up with a way for you to reproduce this crash, but failed.  I DID achieve one crash, but I wasn't able to cause it a second time, thus NOT consistent.

I loaded a Writer document up with Lorem text [I typed Lorem + F3 to create a block of text, and them copy>pasted over and over until the document was 21,504 pages long -- ODT file size 645KB - then I opened FireFox and in FF opened tabs until most Zeroed memory was gone -- according to RamMap -- then I madly scrolled the document, waiting for a crash.  Stable!  So, I opened that O2Ring data file in Calc, and scrolled the hell out of it.  Then more scrolling in the Writer doc, etc.  Then I tried various combinations of closing and opening one, or the other, or both documents, and more scrolling. Finally, a crash happened, but after trying, for a while, to get it to crash again, it wouldn't.  Yet, when I open my book, and try to do a few edits -- CRASH!  And, that recent crash of the O2Ring data file happened before I did ANY of this, and during an Up-Time where I hadn't opened the book document.  So, I'm really sorry, but I haven't succeeded in characterizing this issue, and because so much time has passed, I forget at what release this first presented.

I'm currently using: 

Version: 7.3.6.2 (x64) / LibreOffice Community
Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

My PC is Intel i5-6500 4 cores; BIOS: American Megatrends 2604, 2/22/2018
x64-based PC with 16GB RAM
Baseboard: ASUS Z170-P D3 mode: UEFI

Steps to Reproduce:
Can reproduce but not in a way that I can offer you as a mode.

Actual Results:
Large file -- scroll document -- low on memory -- maybe?

Expected Results:
ALL open LigreOffice documents vanish -- document restore succeeds at restoring from last auto-save.


Reproducible: Sometimes


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
No other
Comment 1 Steve Lawson 2022-10-16 12:25:57 UTC
BTW: I've been using LibreOffice for many years [and before that OpenOffice, because development on LibreOffice seemed to stall.  I worked on my book for much of that time, and I've never had issues like began happening a month or two ago.  I've extensively used Writer and Calc for many different projects.  And, over the last couple of decades I've used either LibreOffice or OpenOffice, avoiding MicroSquish like the plague.  Up until now I've only encountered minor issues, all of which I found a workaround for.  But, this is different, and highly irritating.  I rely on these tools extensively in my work, and of late, find it difficult to get anything done.
Comment 2 m_a_riosv 2022-10-16 13:13:11 UTC
Please past here the information about your version. Menu/Help/About LibreOffice, there is an icon to copy.

Please test running in safe mode, Menu/Help/Restart in Safe Mode.

If nothing works, please play a bit the Menu/Tools/LibreOffice/View - Graphics output options. Like Antialiasing, OpenGL, Skia.
Comment 3 Steve Lawson 2022-10-19 20:27:10 UTC
I turned off OpenGL and stability has returned!  Also, I don't notice any performance degradation.
Comment 4 QA Administrators 2022-10-20 03:45:00 UTC Comment hidden (obsolete)
Comment 5 Buovjaga 2023-02-22 12:11:09 UTC
Yeah, might have been that graphics rendering method Skia/Vulkan. It might be interesting to see the content of your Skia log file:
C:\Users\User\AppData\Roaming\LibreOffice\4\cache\skia.log