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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 2006-05-01 17:53 ------- +I need a test case for this. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
