| 9:53:52 AM PDT - Thu, May 1st 2014 |
|
Hi,
The problem is not in the memory allocation itself. The memory allocator internally checks that the memory blocks are sane. Doing that it has found that memory blocks named "xsm" and "wsm" are corrupted by some memory access that was out of bounds. After detecting this issue the code essentially gives up. I'll if I can track down where this happens as this looks like a real bug.
Best wishes, Huub
|