http://bugs.winehq.org/show_bug.cgi?id=18542
--- Comment #14 from Rein Klazes wijn@online.nl 2009-06-19 02:03:32 --- (In reply to comment #13)
My trace shows the same page fault as all the other traces.
Is that with +heap tracing enabled?
Backtrace:
...
That is something different altogether. I have never seen this.
+heap tracing does that kind of thing. If you reported correctly "A +heap trace takes too long to get anywhere", that is probably why you did not see it.
The menus work fine if you're not streaming, it's when you're streaming that the page fault occurs.
I see 'your' crash here as well (not using +heap tracing) w.o. streaming. With slingplayer to the left, it reliably crashes in RtlFreeHeap or RtlAllocateHeap when choosing exit through the main menu. So far I haven't seen any evidence that the menu code itself is the cause.