Bug 377795 - plasmashell runaway memory usage after switching between external monitors with different resolution
Summary: plasmashell runaway memory usage after switching between external monitors wi...
Status: RESOLVED DUPLICATE of bug 368838
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-19 09:48 UTC by Knut Omang
Modified: 2018-04-30 13:02 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Omang 2017-03-19 09:48:41 UTC
I use a Lenovo Thinkpad T420 laptop, which has Intel integrated graphics (gen 2) and 
runs Fedora 24. If I use the laptop's displayport connector to connect to one external monitor,
then switch to another monitor with a different resolution (eg. from 1920x1200 to 2560x1440) or the opposite) plasmashell (sometimes?) starts a completely runaway memory consumption - 
my laptop has 8G of ram and within a few seconds after plugging into the second monitor, the machine is almost not accessible due to thrashing. 

I have been able to see plasmashell consuming > 5GB of resident memory before I managed to kill it.
It appears to continue to accelerate until the oom killer kicks in.. 
I increased swap space to buy myself some time. 

It happened most recently today, with plasma-workspace-5.8.5-1.fc24.x86_64.
The 1920x1200 was connected via a DVI to displayport adapter, while the 2560x1440 screen was connected with 
a plain displayport cable, if that matters.
Comment 1 Martin Stepnicka 2018-04-29 22:45:34 UTC
The same issue on TP X201.. using plasma 5.12.4
Comment 2 David Edmundson 2018-04-30 13:02:22 UTC
Please reopen if you have the issue with Qt 5.11

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