Closed gjaegy closed 6 years ago
when running a 64-bits build, I get an access violation in the same code instead of an unaligned pointer:
Hey there,
ltmemalign()
call swapped by any chance?-DLTALLOC_SIZE_CLASSES_SUBPOWER_OF_TWO=0
or -DLTALLOC_SIZE_CLASSES_SUBPOWER_OF_TWO=1
to see if it helps?
If it helps, then must be some kind of out of memory issue, I guess.thanks for your reply!
Actually I think my own code creates the corruption :/ I will confirm this later today.
Indeed. I am the guilty one (as one could expect :))
So, will continue evaluating ltalloc. Excellent results so far (at least regarding fragmentation) !
Hi, I have come across an issue where ltmemalign() sometimes returns a pointer that's not aligned correctly.
This occurs with a x86 (32-bits) build, compiled with MSVC 2013.
The requested memory to allocate is 192 bytes, with a 4-bytes alignment.
Any idea ?
Thanks a lot !
PS: the returned pointer value is 0x3f2a3993 (which is clearly not 4-bytes aligned)