Bug 441213

Summary:	[wayland] plasmashell leaks a lot of memory
Product:	[Plasma] plasmashell	Reporter:	Jiri Slaby <jirislaby>
Component:	generic-performance	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kde, nate, wachidadinugroho.maya
Priority:	NOR	Keywords:	wayland-only
Version First Reported In:	5.22.2
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jiri Slaby 2021-08-20 07:34:49 UTC

SUMMARY
After some uptime, plasmashell under wayland eats all the free memory here.

This looks similar to bug 428394 (leak in intel's driver).

STEPS TO REPRODUCE
1. use plasma
2. memory is filled up

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210817
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Kernel Version: 5.13.1-1.gbebf622-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz
Memory: 15.1 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 520

ADDITIONAL INFORMATION
heaptrack at: http://decibel.fi.muni.cz/~xslaby/n/heaptrack.plasmashell.20733.zst

But it is somehow mangled. Heaptrack apparently doesn't support DWARF 5, I see a lot of:
src/interpret/heaptrack_interpret.cpp:351 ERROR:Failed to create backtrace state for module /usr/lib64/qt5/plugins/platforms/libqwayland-generic.so: unrecognized DWARF version in .debug_info at 6 / Success (error code 0)

> $ readelf --debug-dump=info /usr/lib/debug/usr/lib64/qt5/plugins/platforms/libqwayland-generic.so-5.15.2+kde28-1.1.x86_64.debug
> Contents of the .debug_info section:
> ...
>   Compilation Unit @ offset 0x23:
>    Length:        0x3960d (32-bit)
>    Version:       5 <---------------------------
>    Unit Type:     DW_UT_compile (1)
>    Abbrev Offset: 0x0
>    Pointer Size:  8

Comment 1 David Edmundson 2021-08-20 08:31:22 UTC

That heaptrack also shows the vast majority of memory used inside QOpemGlContext::create  

and then going into "optionEE" inside the intel driver.

Comment 2 David Edmundson 2022-01-14 16:04:42 UTC


*** This bug has been marked as a duplicate of bug 428394 ***