2015-05-14, 01:29
because in this wrong situation there are two thread
the first one it's the kodi main thread
the second it's a thread created in dsplayer that performs the stop and restores the textures from madvr to kodi
sometime the thread that come from dsplayer performs the stop before that the main thread try to access to the textures, and everythings goes without error
other times dsplayer it's too slow and kodi tries to access to the textures while DSPlayer is still restoring
normally the stop it's called by the main thread and there is only one thread at work
the first one it's the kodi main thread
the second it's a thread created in dsplayer that performs the stop and restores the textures from madvr to kodi
sometime the thread that come from dsplayer performs the stop before that the main thread try to access to the textures, and everythings goes without error
other times dsplayer it's too slow and kodi tries to access to the textures while DSPlayer is still restoring
normally the stop it's called by the main thread and there is only one thread at work