https://bugs.winehq.org/show_bug.cgi?id=38178 --- Comment #13 from Sergey Isakov <isakov-sl(a)bk.ru> --- (In reply to Stefan Dösinger from comment #12)
It seems odd that 556e3e0c764ee5eff1eb02b97a01d4141d6ec58f would cause a wrong vtable assertion, but it's theoretically possible if there's a random memory corruption.
Which OSX version are you running and which graphics card do you have?
OSX 10.9.5 Radeon Turks XT (as OpelGL see it) == HD6670 2Gb DDR3 wrong vtable assertion appears when I manually changed codes to enumerate display. Original codes lead to error like in comment #9. I will make more tracing to catch exact place where is the memory leak. This commit was just first commit with new methods for memory allocation/release. I have to confirm again that with any my patches/workaround all engines after 1.7.2 crashes at the game started. Wine 1.7.2 and all previous work almost fine. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.