Error in ntdll.dll API
Hi all,
I am inspecting a crash dump from a customer and the current worker thread fails with the following call stack:
> ntdll.dll!ExpInterlockedPopEntrySListFault()
09c3f7f4()
ntdll.dll!RtlAllocateHeap() + 0x14e
ntdll.dll!RtlAllocateHeap() + 0xe2
msvcr71.dll!_heap_alloc(unsigned int size=0x00000100) Line 212 C
msvcr71.dll!_nh_malloc(unsigned int size=0x00000100, int nhFlag=0x00000000) Line 113 C
msvcr71.dll!malloc(unsigned int size=0x00000100) Line 54 + 0xf C
--Application specific code: doing a simple "TheValue = new char[256]" statement.
Please can anyone tell me what are the possible causes for a ExpInterlockedPopEntrySListFault error in ntdll
Thanks a lot in advance.
# 2 Re: Error in ntdll.dll API
I did have the client check the memory usage. There are no known issues with memory. The usage doesnt drastically increase over time and it doesn't seem like the system memory is running out *they use a Intel core duo 3.0Ghz with 3.0Gb Ram* Is it possible that the heap allocated for the application is running out?
# 3 Re: Error in ntdll.dll API
Had the application runned for a long time? Even 3 Gb is finite if application leaks.
Not the same threading model in exe & dlls? (there's another thread discussing that)
S_M_A at 2007-11-9 13:32:41 >

# 4 Re: Error in ntdll.dll API
I did have the client check the memory usage. There are no known issues with memory. The usage doesnt drastically increase over time and it doesn't seem like the system memory is running out *they use a Intel core duo 3.0Ghz with 3.0Gb Ram* Is it possible that the heap allocated for the application is running out?
Not if the memory usage is below 2GB (or 3GB if you have that option enabled). Is the program doing a lot of "new'ing" and "delete'ing"? Maybe the heap is too fragmented.
Viggy
# 5 Re: Error in ntdll.dll API
Not if the memory usage is below 2GB (or 3GB if you have that option enabled). Is the program doing a lot of "new'ing" and "delete'ing"? Maybe the heap is too fragmented.
Viggy
The behaviour is pretty random. The application runs fine for days and sometimes it crashes within 5 minutes. It is a very intensive and critical application and we provide it with a box. We have disabled all the unnecessary services running in Windows. It has only those services and applications absolutely necessary for the application to run. If you can tell me the usual cause of the error and if possible some measures to solve the issues - would really appreciate it.
# 6 Re: Error in ntdll.dll API
The behaviour is pretty random. The application runs fine for days and sometimes it crashes within 5 minutes.
Based on this, and what you've already posted, all I can say is that it sounds like some kind of memory issue. Have you tried running a profiling tool on the application (something like Purify (http://www-306.ibm.com/software/awdtools/purifyplus/win/))?
Viggy