Bug 147608 - Memory usage runs away when Skia is used
Summary: Memory usage runs away when Skia is used
Status: RESOLVED DUPLICATE of bug 149527
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Keywords: haveBacktrace
Depends on:
Blocks: Memory Skia
  Show dependency treegraph
Reported: 2022-02-23 09:43 UTC by philipp-maximilian.bender
Modified: 2023-01-24 02:48 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Produced debug log (35.55 KB, text/plain)
2022-02-24 17:32 UTC, philipp-maximilian.bender

Note You need to log in before you can comment on or make changes to this bug.
Description philipp-maximilian.bender 2022-02-23 09:43:13 UTC
When Skia is enabled in LibreOffice it uses more and more memory till it crashes.
LibreOffice uses memory even faster if the document/calc has some comments.

Steps to Reproduce:
1.1. Open a calc document
1.2. Have Skia enabled
1.3. Scroll through the calc document for some time

2.1 Open a calc/writer document
2.2 Have skia enabled
2.3 Add comments and let them show
2.4 Scroll through the documents for some time

Actual Results:
LibreOffice uses more and more memory till it crashes.

Expected Results:
LibreOffice not crashing due to ne more memory.

Reproducible: Always

User Profile Reset: Yes

Additional Info:
Freeing memory periodically.
Comment 1 V Stuart Foote 2022-02-23 18:41:46 UTC
Please copy paste the Help -> About details for your system. Also, details for your GPU (either the Skia.log if LO is running with Vulkan rendering) or from a run of msinfo32.exe --> on the components Display panel.
Comment 2 philipp-maximilian.bender 2022-02-23 20:07:14 UTC
(In reply to V Stuart Foote from comment #1)
> Please copy paste the Help -> About details for your system. Also, details
> for your GPU (either the Skia.log if LO is running with Vulkan rendering) or
> from a run of msinfo32.exe --> on the components Display panel.

About details:

Version: (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded

GPU details:

Name	Intel(R) UHD Graphics
PNP Device ID	PCI\VEN_8086&DEV_9BC4&SUBSYS_097D1028&REV_05\3&11583659&1&10
Adapter Type	Intel(R) UHD Graphics Family, Intel Corporation compatible
Adapter Description	Intel(R) UHD Graphics
Adapter RAM	1.00 GB (1,073,741,824 bytes)
Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b6a6fe690ab05b2a\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b6a6fe690ab05b2a\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b6a6fe690ab05b2a\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b6a6fe690ab05b2a\igd12umd64.dll
Driver Version
INF File	oem179.inf (iCML_w10_DS section)
Colour Planes	Not Available
Colour Table Entries	4294967296
Resolution	3840 x 2400 x 59 hertz
Bits/Pixel	32
Memory Address	0x4A000000-0x4AFFFFFF
Memory Address	0x0000-0xFFFFFFF
I/O Port	0x00004000-0x0000403F
IRQ Channel	IRQ 4294967269
Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_B6A6FE690AB05B2A\IGDKMD64.SYS (, 29.38 MB (30,809,392 bytes), 15/10/2021 13:29)
Name	NVIDIA GeForce GTX 1650 Ti
PNP Device ID	PCI\VEN_10DE&DEV_1F95&SUBSYS_097D1028&REV_A1\4&1500AB8A&0&0008
Adapter Type	NVIDIA GeForce GTX 1650 Ti, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1650 Ti
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_07d057a43ab2de16\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_07d057a43ab2de16\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_07d057a43ab2de16\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_07d057a43ab2de16\nvldumdx.dll
Driver Version
INF File	oem226.inf (Section161 section)
Colour Planes	Not Available
Colour Table Entries	Not Available
Resolution	Not Available
Bits/Pixel	Not Available
Memory Address	0xB3000000-0xB3FFFFFF
Memory Address	0x70000000-0x81FFFFFF
Memory Address	0x80000000-0x81FFFFFF
IRQ Channel	IRQ 4294967266
Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVDMI.INF_AMD64_07D057A43AB2DE16\NVLDDMKM.SYS (, 40.34 MB (42,298,024 bytes), 15/02/2022 08:38)

LibreOffice should be using the Intel(R) UHD Graphics.
Comment 3 V Stuart Foote 2022-02-23 21:37:29 UTC
You can determine which LO is using from the skia.log file in %APPDATA%\LibreOffice\4\cache

post those details here as well please.
Comment 4 philipp-maximilian.bender 2022-02-24 15:39:13 UTC

RenderMethod: vulkan
Vendor: 0x8086
Device: 0x9bc4
API: 1.2.190
Driver: 0.402.1763
DeviceType: integrated
DeviceName: Intel(R) UHD Graphics
Denylisted: no
Comment 5 V Stuart Foote 2022-02-24 16:53:24 UTC
OK, so it is running Vulkan libs on the Intel GPU with current drivers on a Windows 10 21H2 build, thanks.

HAve you allowed it to report the crash, upload the mini-dump, to the project Crash Report site? Do you have any of the report links?

If not, next step would be to catch the stack at the point of crash, we'd be looking for the call (to GPU or even OpenCL) that are hanging and leaking memory.

A bit tedious to get set up, but could you install the MS WinDbg utility [1] and configure it point to the LO & Microsoft symbols caches [2]

You may be able to run an analyze against a crash dump or forced minidump, but if it just hangs (as it leaks memory) a stack trace "~* kp" is also helpful.

Save the results and attach the text file.

[1] https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools just select the "Debugging Tools for Windows" you don't need any other part of the SDK or the Widnows Driver Kit.

[2] https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#First_Time_Setup
Comment 6 philipp-maximilian.bender 2022-02-24 17:32:55 UTC
Created attachment 178516 [details]
Produced debug log

I hope this log is helpful.
Comment 7 Stéphane Guillou (stragu) 2023-01-23 20:55:46 UTC
Stuart, would you say the part about scrolling in Calc is a duplicate of bug 149527?
Comment 8 V Stuart Foote 2023-01-24 02:43:26 UTC
Yes, the stack trace of attachment 178516 [details] in comment 6 is similar, if not identical and just lacking symbols, with overflow error C0000409 as seen in attachment 178516 [details] on bug 149527 (or dupe bug 150190 ).

*** This bug has been marked as a duplicate of bug 149527 ***
Comment 9 V Stuart Foote 2023-01-24 02:48:55 UTC
Sorry those was attachment 181502 [details] (with symbols) compared to attachment 178516 [details] and  it is a dupe to me.