Re: Paged Pool memory
- From: roger.orr@xxxxxxxxx
- Date: Mon, 17 Nov 2008 03:12:27 -0800 (PST)
On Nov 17, 10:16 am, Harish_38 <Haris...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
When the exception is translated i can see that the exception code is
X_E_NOT_ENOUGH_MEMORY. That explains the orgin of Exception.
This can be a common problem( low resources ).
The problem for crash is stack overflow and i trying to find the reason for
that as this is an uncommon. The exception handling mechanism is allocating
lot of memory(like u said) on the stack and ultimately the stack overflows
before the exception is completely handled.
That's the trouble.
Exception 1 -- caused by original out of memory
Goes into exception handler
tries to allocate lots of memory
fails -- throws another nested exception
Exception 2 -- further down the stack
Goes into exception handler
tries to allocate lots of memoryt
fails...
repeat until no stack left :-)
.
- Follow-Ups:
- Re: Paged Pool memory
- From: Harish_38
- Re: Paged Pool memory
- References:
- Paged Pool memory
- From: Harish_38
- Re: Paged Pool memory
- From: roger . orr
- Re: Paged Pool memory
- From: Harish_38
- Paged Pool memory
- Prev by Date: Doubt related to USB Friendly Name
- Next by Date: Re: how to get a callback from the explorer into my application, when a copyfile is completed
- Previous by thread: Re: Paged Pool memory
- Next by thread: Re: Paged Pool memory
- Index(es):
Relevant Pages
|
Loading