|
|
Dbgview collects messages from _any_ app that generates such messages (e.g. if I'm running snagit, I always see messages from it along with MediaMonkey messages). As to why there's another instance of chrome installed and running on your machine--I have no idea. I just checked Users\Russel\AppData\Roaming\Google and all I see are Android Studio installations. As to "W...exe" I haven't seen anything like that either. Can you recheck? I doubt that any of this is related to MM. |
|
|
I could reproduce the issue most of the time. The error "Window is not loaded yet!" is followed with "Access violation at address 00926545 in module 'MediaMonkey.exe'". It happens after I right-click on the icon in tray bar. I also forgot to mention that, beside of registry file, I copied the original ini file created by program during installation and having only few lines about portable installation. Sorry for the false alarm. I traced the access to the mentioned User folder with Process Monitor and FileWActivityWatch and found that Chrome Portable is doing that every hour or so. I suppose you are right about the debug log file. I am just wondering why just that particular version of Chrome that I mentioned is doing it (120), but not another one (123). The W.. program is WerFault.exe, which is supposed to be a Win error reporting tool. Window is not loaded yet!.png (9,537 bytes) WerFault.exe loaded on error.jpg (67,077 bytes) |
|
|
Fixed |
|
|
Verified 3031 |
- Anonymous
