https://bugs.winehq.org/show_bug.cgi?id=45335
--- Comment #11 from Fabian Maurer dark.shadow4@web.de --- FWIW, I asked someone on #winehackers to test with proprietary drivers, and this is the result: http://paste.debian.net/1029572/. So it's definitely not the driver that's wrong here. I wasn't sure, since proprietary drivers sometimes just hide faulty behavior and it seems to work.
Also, I tested on my VM again, and I must admit I screwed up the test. The VM has had only a tiny amount of RAM, and the program simply ran out of memory. Now that I have it 4GB, the program runs flawless, even with a crazy long path.
There seems to be some issue on wine that runs deeper.