Dont know but maybe thats a start to look into it. Well and hopes may arise when we see how this is evolving.Re: [Wine] Re: malloc small pieces of memory wrote: Well, okay, reading this i started to create a testcase to see the
isolated problem. It seems, that the wine-malloc function behave
differently than malloc with windows.
In the testcase:
1. Allocate three large pieces of memory.
2. Free the second (hopefully middle) piece of memory.
3. Allocate the same size again.
I expect: (3) uses the same memory pointer than the one which was freed
in (2). This is what i get under windows.
With wine, (3) gets a new piece of memory.
This failes, if the pieces are large enough (here: 300 MB), so that
3xMEMSIZE fits into the (virtual) memory, but not 4xMEMSIZE.
<----------------------snipped ----------------------------------------->
<----------------------snipped ----------------------------------------->
Hope you can help me with this.
By the way, i get the same problems when compiling my testcase against
winelib.
Johannes Holzer
P.S.: gcc 3.3.5 with Linux (native!) gives me the same results like
windows.
works great here with wine-0.9.16. minimap is on. can't recognize any flickering. around 20-55 fps.minoan wrote:Patch for wine-0.9.16, nvidia users:
http://minoan.ath.cx/~minoan/wow/wow_patch.diff
/minoan
You are right. Wine has never matched Windows' way of malloc, which is why people made this hack patch. The hack patch won't work on systems with Prelinking (i.e. Fedora) unless you turn off Prelinking (prelink -ua) and then use legacy memory mapping (setarch i386 -L). It's a huge hassle to a long time Wine issue.legine wrote:
It seems, that the wine-malloc function behave
differently than malloc with windows.

Code: Select all
$ wine WoW.exe -opengl
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 144 (GLX)
Minor opcode of failed request: 13 (X_GLXCreateGLXPixmap)
Serial number of failed request: 412
Current serial number in output stream: 413
Code: Select all
$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: GeForce 6600/AGP/SSE/3DNOW!
GL_NVX_conditional_render, GL_SGIS_generate_mipmap, GL_SGIS_texture_lod,
$ glxgears
18936 frames in 5.0 seconds = 3787.136 FPS
16792 frames in 5.0 seconds = 3358.304 FPS
19517 frames in 5.0 seconds = 3903.276 FPS

I get this, or maybe something similar.I've got an interesting problem that I don't think anyone here has posted so far. From time to time, my movement keys will "stick," causing me to continue running in a certain direction until I push the key again.
Try ctrl+printscreen key. Printscreen key is around the top-right somewhere.Garnett wrote:I would take a screenshot of this phenomenon but I'm not sure how to do that...
then you haven't installed the patch, which you need.asheron wrote:what the hell do i do with the minimap package i was told to download, does anyone ever give instructions???
btw does anyone have problems using their cursor in wow? i cant select npc's, monsters, even other players. it seems as if my cursor is limited to the toolbars, when i try to use first, and right click, it only changes my view. Evenn when i leave it only the corpse for a while, i still cant loot it.
YES i drink WINE, from a box.