[kaffeine] [Bug 403803] Memory leak in Kaffeine when using deinterlacing
https://bugs.kde.org/show_bug.cgi?id=403803 Mauro Carvalho Chehab changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #7 from Mauro Carvalho Chehab --- (In reply to Petr Kovács from comment #5) > So i tried nvidia drivers (390.116) instead of nouveau and there is no > problem with leaking memory. As this sounds to be an issue with the GPU driver, I'm closing this bug. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403803] Memory leak in Kaffeine when using deinterlacing
https://bugs.kde.org/show_bug.cgi?id=403803 --- Comment #6 from Mauro Carvalho Chehab --- (In reply to Petr Kovács from comment #5) > So i tried nvidia drivers (390.116) instead of nouveau and there is no > problem with leaking memory. Ok. I guess that the best would be if you would open a BZ at freedesktop reporting the issue with the nouveau driver. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403803] Memory leak in Kaffeine when using deinterlacing
https://bugs.kde.org/show_bug.cgi?id=403803 --- Comment #5 from Petr Kovács --- So i tried nvidia drivers (390.116) instead of nouveau and there is no problem with leaking memory. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403803] Memory leak in Kaffeine when using deinterlacing
https://bugs.kde.org/show_bug.cgi?id=403803 --- Comment #4 from Mauro Carvalho Chehab --- (In reply to Petr Kovács from comment #3) > Mauro, I'm not sure if we understand each other. The problem occurs when you > set deinterlacing method to "discard". When you disable deinterlacing or use > another method than discard, everything is fine. > > When discard is selected, Kaffeine's memory consumption grows by 23 MiB each > time TOP refreshes (which is every 3 seconds on my computer). At this rate, > you are out of memory in a few minutes (depending on your RAM size of > course). Wow! I can't reproduce this behaviour here. Anyway, it is libvlc with handles de-interlacing. Here, I'm using version 3.0.6, with is the latest stable one while playing a *.mp4 file. No memory consumption increase on such rate (it has a small increase at the beggining, while libVlc is doing some buffering). With DVB, memory consumption may grow with time, due to EPG data. > > I'm using nouveau graphics driver on GeForce GTX460. I will try to install > the proprietary nvidia drivers and check if that helps. I would rely a lot more on nouveau than with nvidia proprietary driver. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403803] Memory leak in Kaffeine when using deinterlacing
https://bugs.kde.org/show_bug.cgi?id=403803 --- Comment #3 from Petr Kovács --- Mauro, I'm not sure if we understand each other. The problem occurs when you set deinterlacing method to "discard". When you disable deinterlacing or use another method than discard, everything is fine. When discard is selected, Kaffeine's memory consumption grows by 23 MiB each time TOP refreshes (which is every 3 seconds on my computer). At this rate, you are out of memory in a few minutes (depending on your RAM size of course). I'm using nouveau graphics driver on GeForce GTX460. I will try to install the proprietary nvidia drivers and check if that helps. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403803] Memory leak in Kaffeine when using deinterlacing
https://bugs.kde.org/show_bug.cgi?id=403803 --- Comment #2 from Mauro Carvalho Chehab --- Memory leak issues are hard to detect and fix, specially on GUI apps, as Qt and glib do internal allocations that are freed at their will, with not much control from the application. I took some time to identify several cleanups at Kaffeine, in order to solve memory leaks, specially at backend-vlc. After those, playing a mp4 video movie, with deinterlaced OFF, I'm getting those results: PID PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND - 9690 20 0 2347836 191212 129664 S 2,3 0,6 0:04.31 kaffeine 00:00 9690 20 0 2611344 206048 130168 S 4,0 0,6 0:05.18 kaffeine 01:00 9690 20 0 2611472 209280 130232 S 3,3 0,6 0:07.06 kaffeine 03:00 9690 20 0 2611472 213044 130300 S 3,0 0,6 0:11.15 kaffeine 08:00 9690 20 0 2612368 213852 130300 S 3,3 0,7 0:21.43 kaffeine 11:00 9690 20 0 2611472 213852 130300 S 3,3 0,7 0:27.60 kaffeine 15:00 9690 20 0 2611472 213852 130300 S 4,0 0,7 0:36.36 kaffeine 18:00 9690 20 0 2612092 214100 130548 S 3,7 0,7 0:42.15 kaffeine 26:00 9690 20 0 2613160 215180 131616 S 3,3 0,7 0:58.23 kaffeine - 9690 20 0 2348776 214304 130736 S 0,0 0,7 1:00.49 kaffeine It is natural to have some variance on allocated memory, but the above doesn't seem absurd to me. While valgrind still points to some memory leaks at backend-vlc, none seem to be happening while the video is playing. They could very well be false-positives. That's said, de-interlacing code is internal to libVlc and to accel libraries (like vaapi). Here, I'm using open source i965 driver with an Intel board. I suspect that using a closed source driver would produce a way worse result, as I've heard about bad things that would be happening with memory allocation on such drivers. It should also be noticed that it is expected that digital TV playing would steadily increase the memory consumption as new EPG entries are added. I didn't try yet to address eventual memory leaks at the DVB part of Kaffeine's code, as we need first to address the leaks at the VLC backend. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403803] Memory leak in Kaffeine when using deinterlacing
https://bugs.kde.org/show_bug.cgi?id=403803 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- I can reproduce with Kaffeine 2.0.16 on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
