Version: 2.0-SVN (using 4.1.00 (KDE 4.1.0), MS Visual Studio 2005 SP1) Compiler: cl.exe OS: Microsoft Windows (i686) release 5.1 (XP Professional) This is a strange problem: I have all of my data on an ext3 hard drive that I load from Windows. I set Amarok to grab this music from my home directory on this drive, and everything seems fine. But if album art is displayed (for example, when changing the sorting of music, or adding to the playlist and scrolling down to an album that actually has art), amarok crashes. I am really excited that I have Amarok in Windows. I boast about how it's the greatest music player ever, and hopefully soon I can demonstrate its awesomeness in both Linux and Windows! (Preferably Linux, though. ;) )
After checking again, it crashes after every "Fetching Album Art" message, but only after the process is 100% complete. But the progress bar sits there at 100% for about a second and then Amarok crashes.
Oops, the message actually reads "Fetching Cover". It hits 100% and then crashes.
Try to get a backtrace please.
How do I do that in Windows?
I figured out how and will get you one as soon as I boot back into windows later.
Ok, re-open when you have the backtrace.
Created attachment 26929 [details] Amarok backtrace from the crash. This would be better if there was an option to turn off cover fetching (and covers all together) but this is what causes the crash.
Done!
It looks like the problem is related to lack of proxy handling. Go figure. I hate proxies. <_< Anyway, as I said, the option to disable album art, or at least album art fetching, would be nice.
That isn't a backtrace, thats just the output from console.
Automatic album art fetching can now be disabled.
Created attachment 26936 [details] The actual backtrace. I think this is what you guys are looking for. I got this with windbg.
(I don't know whether you wanted me to reopen this when I posted the backtrace, buy I'm guessing "yes")
Updated the description, as I cannot reproduce the crash and do not use a proxy.
Dan: Is this going to happen for beta 2? Or do we move it to 3?
Closing this report for old age. Also the backtrace isn't enlightening to me. Please feel free to reopen this report if it should still happen with a current Amarok build (2.1-something).
Closing for lack of feedback. Most likely fixed in current 2.2-git.