<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Memory leak in drm_atomic.c eventually (few days) consuming all RAM (on at least one system configuration)" href="https://bugs.freedesktop.org/show_bug.cgi?id=98420#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Memory leak in drm_atomic.c eventually (few days) consuming all RAM (on at least one system configuration)" href="https://bugs.freedesktop.org/show_bug.cgi?id=98420">bug 98420</a> from <a class="email" href="mailto:felix.monninger@gmail.com" title="Felix Monninger <felix.monninger@gmail.com>"> Felix Monninger</a> <pre>Oh I see. Interesting to learn about the different approaches to these matters. As a final note on when this bug occurs and why it hasn't been noticed yet (this might be useful for people finding this until the time at which the patched code is distributed): Programs like "xflux" or "redshift" that change screen color temperature to a more reddish type depending on daytime will trigger a call of drm_atomic_helper_legacy_gamma_set(). During transition phase (from normal->red and vice versa) they make many (>100) calls, and then in regular intervals (xflux: every 0.5s; redshift: every 5s). Thus at each of these intervals memory is leaked, with redshift at 1/10 the rate of xflux. With these tools turned off there don't seem to be many changes of the gamma value. So this bug will probably not affect those who are not using these tools. Also, this has been introduced only recently, > kernel 4.5.1 (If everything is wrapped up, this issue can be closed, but I don't know the correct procedure.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>