by rusty » Sat May 08, 2021 11:52 pm
rcherry wrote: ↑Sat May 08, 2021 2:07 pm
What that means exactly, I have no idea.
It might sound a bit ominous, but it won't take that long to send us a debug log. Here's what you do:
1) Install
https://www.mediamonkey.com/beta/MediaM ... _Debug.exe (don't run it yet)
2) Download the DbgView application from:
http://technet.microsoft.com/en-us/sysi ... s/bb896647
3) Generate the debug log:
- Execute DbgView.
- Execute MediaMonkey.exe and reproduce the bug
--> You'll see logs being generated in DbgView (if not try running DBGView as Administrator)
- Save the log messages from DbgView to a file, compress it (ZIP, RAR). If the file is too large ( > 2MB) then upload the file to a free file hosting service (DropBox, RapidShare, FileDropper, MediaFire, ...).
4) If a crashlog dialog appears, copy the crashlog ID
5) Open a ticket in our
helpdesk and send the debug log (and crashlog ID) with reference to this thread.
Thanks so much for your help!
-Rusty
[quote=rcherry post_id=481225 time=1620500822 user_id=24960]
What that means exactly, I have no idea.
[/quote]
It might sound a bit ominous, but it won't take that long to send us a debug log. Here's what you do:
1) Install https://www.mediamonkey.com/beta/MediaMonkey_5.0.1.2402_Debug.exe (don't run it yet)
2) Download the DbgView application from: http://technet.microsoft.com/en-us/sysinternals/bb896647
3) Generate the debug log:
- Execute DbgView.
- Execute MediaMonkey.exe and reproduce the bug
--> You'll see logs being generated in DbgView (if not try running DBGView as Administrator)
- Save the log messages from DbgView to a file, compress it (ZIP, RAR). If the file is too large ( > 2MB) then upload the file to a free file hosting service (DropBox, RapidShare, FileDropper, MediaFire, ...).
4) If a crashlog dialog appears, copy the crashlog ID
5) Open a ticket in our [url=https://www.mediamonkey.com/support/]helpdesk[/url] and send the debug log (and crashlog ID) with reference to this thread.
Thanks so much for your help!
-Rusty