https://bugs.kde.org/show_bug.cgi?id=403803
Mauro Carvalho Chehab changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
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
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.
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
> anoth
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
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 ide
https://bugs.kde.org/show_bug.cgi?id=403803
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--- Comment #1 from Patrick
