[Mono-bugs] [Bug 54133][Blo] Changed - Thread.Abort is not implemented on windows.

[bugzilla-daemon@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 liyul@hotmail.com.

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

--- shadow/54133	2004-02-10 03:54:01.000000000 -0500
+++ shadow/54133.tmp.18174	2004-02-10 22:00:09.000000000 -0500
@@ -3,13 +3,13 @@
 Version: unspecified
 OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
 Severity: Unknown
-Priority: Normal
+Priority: Blocker
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: liyul@hotmail.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
@@ -156,6 +156,39 @@
 from 90 to 9000000 and still had the same error.
 
 ------- Additional Comments From gonzalo@ximian.com  2004-02-10 03:53 -------
 That must be running mono under windows. See
 mono/mono/metadata/threads.c... Thread.Abort is not implemented on
 windows. I'm CC'ing Dick.
+
+------- Additional Comments From liyul@hotmail.com  2004-02-10 22:00 -------
+It's under windows 2000 server. I've managed to trace a bit more
+deeper before it crashes. Anyway, Thread.Abort should almost "NEVER"
+be called by good code unless absolutely necessary (like stopping the
+Nuke war by any means). And in our aspx, we didn't have any such code.
+So I still hope that we could track it down and fixed ASAP.
+
+Thanks a million.
+
+do { HttpApplication.StateMachine.ExecuteNext
+Enter ExecuteState in HttpApplication.StateMachine.ExecuteState 386489952
+before _app.Context.BeginTimeoutPossible in
+HttpApplication.StateMachine.ExecuteState
+after _app.Context.BeginTimeoutPossible in
+HttpApplication.StateMachine.ExecuteState
+before state.Execute in HttpApplication.StateMachine.ExecuteState
+System.Web.HttpApplication+ExecuteHandlerState
+Enter HttpApplication.ExecuteHandlerState.Execute
+before ProcessRequest in HttpApplication.ExecuteHandlerState.Execute
+Enter ProcessRequest in System.Web.UI.Page
+before InternalProcessRequest in System.Web.UI.Page.ProcessRequest
+Enter InternalProcessRequest in System.Web.UI.Page
+aspx.page, Begin Init
+aspx.page, End Init
+before LoadRecursive in System.Web.UI.Page.InternalProcessRequest
+Enter LoadRecursive in System.Web.UI.Control
+before OnLoad (EventArgs.Empty); in System.Web.UI.Control.LoadRecursive 
+Enter OnLoad in System.Web.UI.Control
+before if (eh != null) in System.Web.UI.Control.OnLoad System.EventHandler
+before eh(this, e) in System.Web.UI.Control.OnLoad System.EventHandler
+
+How to I quickly find out which EventHandler is killing me?