I am working on a large application written in VB.Net 2003. Sometimes the application just closes for no reason, without any warning or error messages. The application does not go through the standard closedown code - it's as if execution just stops.
Does anyone know of any circumstances where this could happen, i.e. possibly framework bugs Or point me in the direction of debugging help!
Thanks!
Mark
Unexpected program closure
Hot Topic
- Oracle 9i & .NET - problems with character sets
- Losing callback subscription in remote object delegate event
- xsd.exe generated dataset type problems
- Checking whether a server using TcpListener is broadcasting.
- Using Configuration Classes
- Checking internet connection
- How to open an webapplication that is copied from another machine
- Error Massage after deploying in client...
- Can somebody tell me how exactly we handle Concurrency Violation.
- C# -How to access a shared folder in other machine?
.NET Development
- How to get a list of all assembly dependencies and their complete file paths ?
- How to access store procedure from oracle
- How Often To Open/Close Connections w/ Datareader
- Interpreting the data from database schemas
- FTP Help in asp.Net 1.1
- Arrays/Trees In the Registry
- ObjectDataSource doesnt read ReadOnly columns
- WinForms Vs WebForms
- Update not writing default values to the database
- Problem with TransactionScope and Swedish OS
Unexpected program closure
Annoyeddeveloper
The program has shutdown when left running over night, so no users in the office to terminate task. Also the windows user account doesn't have permission to do that.
I guess it could be a stack-overflow issue - I will leave the application running over night with Visual Studio debugger attached and see if that catches anything.
Any other suggestions of possible causes
Many thanks
Mark
GRoston
Are you sure no shutdown code is running There are at least 2 ways this can happen:
1. Something forcibly + rudely closes it (eg, TaskMan : EndProcess)
2. when an unmanaged thread has an 2nd-chance stack-overflow exception. In those cases, the OS will just rip the process down without any warning.
Try running it under a native-only and mixed-mode debugger and look for any exceptions.
Mike
http://blogs.msdn.com/jmstall
OzJester
Note that when the debugger is attached, it can be attached as managed-only, interop (mixed), or native-only.
For this case, I'd recommend trying native-only.
Mike
http://blogs.msdn.com/jmstall