Bug 371829 - mediaframe reading files even after all plasmoids where removed
Summary: mediaframe reading files even after all plasmoids where removed
Status: RESOLVED FIXED
Alias: None
Product: kdeplasma-addons
Classification: Unmaintained
Component: Media Frame (other bugs)
Version First Reported In: 5.8.2
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-29 17:16 UTC by Luiz Angelo De Luca
Modified: 2020-01-02 15:34 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luiz Angelo De Luca 2016-10-29 17:16:00 UTC
Hello,

I'm using plasma5-addons-5.8.2-1.1.x86_64 from OpenSUSE Tumbleweed.

I noticed that my plasma was eating CPU and with strace -e "read,open" -p $(pidof plasmashell), I checked that it was frequently opening and reading the media I used in the mediaframe. The problem is that it keeps doing that even after the plasmoid was removed. As I added/removed the plasmoid a bunch of times, plasma was openning and reading the same media files a bunch of times per second!

This is the frequency of each syscall during a few seconds monitoring:

3 mmap
3 munmap
4 access
5 write
16 lstat
23 ioctl
35 statfs
70 getdents
90 writev
270 fcntl
305 close
306 open
577 fstat
804 lseek
2825 stat
5107 read
16926 recvmsg
17230 poll
33774 futex

read and open are almost exclusively generated by mediaframe (and probably others).

As a workaround, I moved the files, which might generate a read error and somehow stopped the loop process. My cpu usage, then, reduced from 160% to 40%.

BTW, it would be nice to have mediaframe on bugzilla components list
Comment 1 Nate Graham 2020-01-02 15:34:57 UTC
Cannot reproduce; this doesn't seem to be a problem anymore.