[Mono-bugs] [Bug 78260][Nor] Changed - CPU hog/hang in low memory with complex ASP.NET pages

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon May 1 17:53:19 EDT 2006


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 gonzalo at ximian.com.

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

--- shadow/78260	2006-05-01 17:44:26.000000000 -0400
+++ shadow/78260.tmp.8275	2006-05-01 17:53:19.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 78260
 Product: Mono: Tools
 Version: 1.1
 OS: GNU/Linux [Other]
 OS Details: Gentoo
-Status: NEW   
+Status: NEEDINFO   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: mod_mono
 AssignedTo: gonzalo at ximian.com                            
 ReportedBy: rlyon at novell.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -20,6 +20,9 @@
 never returns) with complex ASP.NET. We don't understand the whole 
 situation, but when the ASP.NET page includes a large number of 
 components (ascx components) (6 in our case) on a machine with lower 
 memory (640M) the mono process will hog the CPU during the compilation of 
 the page and never return. When we lowered the number of components the 
 compilation of the page completed successfully.
+
+------- Additional Comments From gonzalo at ximian.com  2006-05-01 17:53 -------
+I need a test case for this.


More information about the mono-bugs mailing list