<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Cursor sprite sometimes not showed since linux 5.2" href="https://bugs.freedesktop.org/show_bug.cgi?id=111541#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Cursor sprite sometimes not showed since linux 5.2" href="https://bugs.freedesktop.org/show_bug.cgi?id=111541">bug 111541</a> from <a class="email" href="mailto:jadahl@gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>Created <a href="attachment.cgi?id=145329" name="attach_145329" title="dump-gbm-bo.c">attachment 145329</a> <a href="attachment.cgi?id=145329&action=edit" title="dump-gbm-bo.c">[details]</a> dump-gbm-bo.c Using the attached function (compile, break the compositor process using gdb, then run "print dlopen("/path/to/compiled/dump-gbm-bo.so", 2)") I attempted to look at the contents of the cursor buffer before it was passed to drmModeSetCursor2(). When reproducing, it seems that it contains only 0s, but the rest is correct (e.g. size). When it's not reproducing, the dump at the equivalent timing shows correct content. I haven't verified that a dump of the same gbm_bo is correct immediately after writing pixels. In the cursor renderer code in mutter, we only ever write to a gbm_bo immediately after its construction, and we never map the memory after that. As the case is that this only reproduces with some kernel versions, I have my doubt it's that we upload empty pixels, but will add some code that dumps after construction too to be sure. What could cause memory of a gbm_bo to be cleared after its construction, but before its destruction?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>