Issue with Discord RPC
Opened this issue · 10 comments
Upon replicating the issue, I found that it is handled by the library and the stack trace is printed no matter what. In fact, when you run two instances and close the first one, the rich presence still persists. I suppose a check could be added though since it seems to be in the same place every time.
Can someone on a mac/linux give the location of their dll's? that way i can add a checker to see if it is in use because y not
what dlls
see the image and replicate the issue and provide the location of the file in use (if it even works at all)
runs just fine
or not. the first instance just crashed but not for the same reason
the.thing.mp4
Thanks i think its handled by the lib so i won't look into a fix
Thanks i think its handled by the lib so i won't look into a fix
if we cant be bothered to check it ourselves we can try to catch that error. bad code but i don't see alternatives .
It cant be caught since the library catches it and prints the stack trace