I want to know in which scenario this message will be displayed
Though I dont know exactly the reason, one possible theory could be heapfree is called and again dlmfree is called. it could be dlmfree is trying to free the same regions freed by heapfree and getting PF
or
dlmfree is trying to access invalid page which could have been marked noaccess by kernel, but the driver does not know it yet.
It will be helpful if i get dlmalloc.c file to debug further.
I am not sure if you would get access to dlmalloc.c from VMware, but dlmalloc.c is opensourced from linux
http://www.cs.virginia.edu/~wh5a/personal/House-0.8.92/kernel/user/dlmalloc.c