Bug in MediaMonkey v4.1.0.1691

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Bug in MediaMonkey v4.1.0.1691

Re: Bug in MediaMonkey v4.1.0.1691

by richy3892 » Mon Feb 03, 2014 3:25 pm

Thanks, I'll just wait it out till 4.1.1 then.

Re: Bug in MediaMonkey v4.1.0.1691

by Lowlander » Mon Feb 03, 2014 11:34 am

This is something set to be tackled in 4.1.1: http://www.ventismedia.com/mantis/view.php?id=11799

Bug in MediaMonkey v4.1.0.1691

by richy3892 » Sun Feb 02, 2014 3:01 pm

There is a bug in MediaMonkey v4.1.0.1691. It crashes on scanning the files ("Scan at startup" enabled), apparently because one file name is longer than 259 characters, because after renaming the file, MediaMonkey didn't crash anymore. It's running on Windows 7 x64 Home Premium and although I've installed the debug version, there is no MediaMonkey.elf to see in "C:\Program Files (x86)\MediaMonkey" or "C:\Users\<user>\AppData\Roaming\EurekaLog\MediaMonkey" (the directory EurekaLog doesn't exist). Apparently it crashes before automatically sending the log, because I don't get prompted for that.

Top