<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - spice-gtk out of memory when guest os replay vedio" href="https://bugs.freedesktop.org/show_bug.cgi?id=93497#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - spice-gtk out of memory when guest os replay vedio" href="https://bugs.freedesktop.org/show_bug.cgi?id=93497">bug 93497</a> from <a class="email" href="mailto:bugzilla@victortoso.com" title="Victor Toso <bugzilla@victortoso.com>"> Victor Toso</a> <pre>(In reply to linp.lin from <a href="show_bug.cgi?id=93497#c3">comment #3</a>) > Thank you for reply. > i have found that, display data was handle by display_handle_stream_data, > when CPU in high load, data was save in st->msgq, after long time run, the > queue is very long. The system has been run out of memory. Right! I can see that the memory will grow on high CPU usage (which can happen easy with streaming, I guess). The memory of st->msgq is released on the coroutine context... As I don't have an ARM to test the debug information and the valgrind output will be useful anyway. Please attach the output of spicy with --spice-debug so I can see how everything is being handled in your environment</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>