Enough of them usually crashes the iStripper Player.
the RandomShadres.exe has no impact on the iStripper player.
( it interfaces with the PC's Keyboard buffer, and pushes a Key stroke to the Buffer.
Specifically the Down Arrow Key )
Just prior to pushing the Down Arrow on to the Keyboard Buffer, it tells the OS, give the focus to the Process with the Process ID of 'nnnnn'
Since the OS then hands the focus to iStripper, it is the App that gets the next Keyboard key strokes.
The iStripper app then sees the Down arrow having been pressed on the Keyboard.
No Direct connection between the RandomShadrers App and iStripper.
iStripper crashes are not related to the RandomShaders app.
I have noticed many crashes while using fullScreen without the randomshaders use.
especially scenes using shaders.
I have also noticed many times, white Boxes where the models should be, prior to crashes on Scenes that aren't using shaders.
This sometimes happens, where there is a Long Delay, before the Scene starts. ( probably a Memory Leak )
Monitoring Memory, I do see there may be a GPU memory leak, but I can't repetitively cause it to happen and I've only been monitoring it once or twice that I saw it happen.
But Nothing that I can ***** to happen so I can't write a report with Steps to make it happen.
Here is one example that I captured while monitoring after a crash and restart.
iStripper was idle no models playing, but the Memory was climbing, got to over 7GB of Memory.
While at the same time my Internet was Maxed out by iStripper, but wasn't able to discover what was being downloaded.
I'm not able to replicate this consistently.
https://virtuastripper.net/video/iStripper-Idle-Memory-leak-001.mp4This error: Process 'nnnn' was not foundis Because the iStripper app is No longer found.
It is either Not responding, or it has crashed
The OS tells the RandomShader app, the Process ID you told me to give the focus too, doesn't exist.
and the RandomShaders app reports the error.