Fix the System.AccessViolationException bug in the Library
There is a bug that makes the Library impossible to use for some users, possibly related to how MediaMonkey itself handles errors.
This bug is very rare, and I (the developer) have been completely unable to reproduce it. It is thus very hard to debug.
If somebody that experiences this bug would allow me to remote control their computer, I might be able to figure it out. It would, of course, happen in such a way that the user could see everything I was doing, and could cancel it at any time.
I would need to be able to look around at system properties (installed frameworks, MediaMonkey settings), and possibly, if the user is very kind, install Microsoft Visual Studio to actually be able to debug the problem directly on this computer.
I can't give much in return, but if someone would allow me to do this, the reward would be a possibly working Library browser, and I'd certainly reward them free bonus features if that would be interesting.