search

srix55 / media_kit_win_mem_test

To see if there's any memory leaks over longer durations of repeated player creation in windows
0 stars 0 forks source link

GLib-ERROR **: 17:40:06.591: creating thread 'mpv_render_context_set_update_callback': Error creating thread: Resource temporarily unavailable #1

Open ZG-123 opened 1 year ago

ZG-123 commented 1 year ago

Sorry to bother you, but I have encountered the same problem as you in the issues of media_kit. I would like to ask if you have solved this problem. I have also encountered this problem now, and I don't know how to solve it.

srix55 commented 1 year ago

I haven't solved it. The author of media_kit suggests using pools of reusable players and recycle through them and destroy them only on app exit (not screen or widget exit) - still not sure if clearing the playlists causes memory leaks. I have not yet tested that. The media_kit demos dispose off players only on exit of app, so memory crashes don't happen there, as far as i know.

ZG-123 commented 1 year ago

Thank you for your reply. In my actual scene, cameras need to be added and deleted, so dynamic player destruction is still needed. I will continue to work hard to find a solution, thanks again.

srix55 commented 1 year ago

I am in the same boat. Let me know when you find a solution to this. Thanks.

ZG-123 commented 1 year ago

After testing, I created three players, which are computer native camera, webcam and USB camera, directly play the video picture, about ten minutes or so, the key is that this has not been destroyed, it will also report the error.

srix55 commented 1 year ago

Is the memory leak happening? Does the app crash over long durations?

ZG-123 commented 1 year ago

I used three cameras, a PC local, a USB port and a webcam, which would crash if left on for about 15 minutes. Mine will still report the error: Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory.