http://bugs.winehq.org/show_bug.cgi?id=28087
--- Comment #7 from Jonas Nyrén jonas.nyren@gmail.com 2011-08-15 18:44:56 CDT --- I'm having some difficulties prodivind you with a crash reproduction based on just one mp3.. This thing only seems to be triggered when you have a sufficiently big library (as for how big that is, I don't know. 450 tracks seems to be enough). I'm guessing it's because of some delays created by querying the database for autocompletion of tags.. Anyway, I shall try to give as detailed a description as I can.
1. Get foobar2000 from www.foobar2000.org (1.1.7 - latest stable is what i use, but the same crash happens with much older versions. 1.1.1 for example) 2. Install (standard install, launch it at the end of installer) 3. Just press OK in the quick layout dialog 4. Go to menu library->configure 5. remove the existing directory and add a directory where you have your mp3s, press OK --wait for it to scan the collection (you don't get any visual confirmation of when it's done other than status in library->configure changes from "initializing.." to "monitoring"-- 6. Bring up library->album list 7. add some tracks from the album list by drag and drop or right click->add to current playlist 8. Select the tracks in the playlist and hit alt+enter or right click->properties 9. Select composer field and enter Some values separated by semicolons ';' I.E. Somecomposer; Anothercomposer; Whathaveyou and here it will crash "eventually". For a large'ish collection (mine is around 10k tracks) it will almost always happen somewhere after the first semicolon. when I tested with a smaller collection (~450 tracks) it eventually happened after the second semicolon.. I can't really narrow it down to some specific case where it happens more than that :( But it's for certain that this crash is definitely related to autocompletion and it is also certain that it _does_ crash in 1.3.26 but _doesn't_ crash in versions up to and equal to 1.3.25.
I hope that helps, if not ask me for more info I can provide. The program monitors itself and when it crashes it sends up a "send bugreport" dialog so there is nothing (no backtrace, or meaningful messages) in the console output i can give you.