[Mono-bugs] [Bug 75267][Cri] New - crash during web request in ASP.NET

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by matt.hargett at logiclibrary.com.

http://bugzilla.ximian.com/show_bug.cgi?id=75267

--- shadow/75267	2005-06-14 17:44:11.000000000 -0400
+++ shadow/75267.tmp.8098	2005-06-14 17:44:11.000000000 -0400
@@ -0,0 +1,79 @@
+Bug#: 75267
+Product: Mono: Class Libraries
+Version: 1.1
+OS: SLES 9
+OS Details: x86-64  
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Critical
+Component: Sys.Web
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: matt.hargett at logiclibrary.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: crash during web request in ASP.NET
+
+Description of Problem:
+Several customers have reported HTTP 500 errors with the stack trace below
+while using our ASP.NET web UI. 
+
+
+Steps to reproduce the problem:
+1. in our web app, upload a file
+2. view a report
+3. click on a report item
+
+Actual Results:
+Server error in '/' application
+
+--------------------------------------------------------------------------------
+
+Description: Error processing request. 
+
+Error Message: HTTP 500. 
+
+Stack Trace: 
+
+System.InvalidOperationException: Process has not been started.
+in <0x00051> System.Diagnostics.Process:get_ExitCode ()
+in (wrapper remoting-invoke-with-check)
+System.Diagnostics.Process:get_ExitCode ()
+in <0x001d5> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromFileBatch
+(System.CodeDom.Compiler.CompilerParameters options, System.String[] fileNames)
+in <0x00322> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromDomBatch
+(System.CodeDom.Compiler.CompilerParameters options,
+System.CodeDom.CodeCompileUnit[] ea)
+in <0x0003e> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromDom
+(System.CodeDom.Compiler.CompilerParameters options,
+System.CodeDom.CodeCompileUnit e)
+in <0x00132> System.Web.Compilation.CachingCompiler:Compile
+(System.Web.Compilation.BaseCompiler compiler)
+in <0x00237> System.Web.Compilation.BaseCompiler:GetCompiledType ()
+in <0x00107> System.Web.Compilation.AspGenerator:GetCompiledType ()
+in <0x0002f> System.Web.UI.PageParser:CompileIntoType ()
+in <0x00011> System.Web.UI.TemplateControlParser:GetCompiledInstance ()
+in <0x0003b> System.Web.UI.PageParser:GetCompiledPageInstance
+(System.String virtualPath, System.String inputFile, System.Web.HttpContext
+context)
+in <0x00010> System.Web.UI.PageHandlerFactory:GetHandler
+(System.Web.HttpContext context, System.String requestType, System.String
+url, System.String path)
+in <0x00294> System.Web.HttpApplication:CreateHttpHandler
+(System.Web.HttpContext context, System.String type, System.String file,
+System.String path)
+in <0x0008f> System.Web.HttpApplication+CreateHandlerState:Execute ()
+in <0x0007c> System.Web.HttpApplication+StateMachine:ExecuteState
+(IStateHandler state, System.Boolean readysync)
+
+
+Expected Results:
+Shouldn't crash.
+
+How often does this happen? 
+It seems to happen intermittently, and can be difficult to reproduce.
+Several different customers and prospects have reported it, however.
+
+Additional Information: