Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919413, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b01 - by mogadan

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 491888 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/24/2009 9:10:40 AM
Access Restriction Public

Description

have a code in ASP.NET Application that use unmanaged resources.

this code goes for a list of objects and make some operations with Unmanaged Interop.

this code wrapped by lock to prevent concurency execution.
private static object one_renderer_at_time = new object();
...
lock(one_renderer_at_time ) 
{
// code here
}


Code inside lock works fine if One Request comming to server. But if in time when this code running Second request comes( either to anoter page taht is not run this code ),  IIS workerProcces crashed with error:

Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919413, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b01


I'm pretty sure that I'm cleanup all unmanaged resources after use. Memory usage of IISWorkerProccess is stable aprox 300Mb. In Any case, i think, this should not  be a cause of crash.





Sign in to post a comment.
Posted by Microsoft on 9/29/2009 at 2:03 PM
It's difficult for us the work through the code which you've provided as a repro. Do you have a simpler code snippet which also reproduces this behavior?
Posted by Microsoft on 9/29/2009 at 2:03 PM
It's difficult for us the work through the code which you've provided as a repro. Do you have a simpler code snippet which also reproduces this behavior
Posted by Microsoft on 9/29/2009 at 2:00 PM
It's difficult for us the work through the code which you've provided as a repro. Do you have a simpler code snippet which also reproduces this behavior.
Posted by Microsoft on 9/27/2009 at 9:50 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Posted by mogadan on 9/24/2009 at 10:00 AM
UPDATE2: cancel Update1, reproduce without GC.Collect
Posted by mogadan on 9/24/2009 at 9:27 AM
UPDATE: seems that error reproduced only if have GC.Collect inside a loop
Posted by mogadan on 9/24/2009 at 9:12 AM
code snippet attached