objectdisposedexception

I have a C# WPF UI app, and when I close it, I always get a windows application-crash dialog ("UIDemo has encountered a problem and needs to close."). The error report indicates that it's a System.ObjectDisposedException which indicates that somewhere a method's being called on a disposed object. That's fine, I do understand that part. And I would love to fix it. I just can't get a stacktrace on the bastard. That exception is evading all of the following: my DispatcherUnhandledException handler my try/catch surrounding the entire contents of the Exit event handler clicking "Debug" in that

ive checked out some of the other questions and obviously the best solution is to prevent the behavior that causes this issue in the first place, but the problem is very intermittent, and very un-reproduceable. I basically have a main form, with sub forms. The sub forms are shown from menus and/or buttons from the main form like so: private void myToolStripMenuItem_Click(object sender, EventArgs e) { try { xDataForm.Show(); xDataForm.Activate(); } catch (ObjectDisposedException) { MessageBox.Show("ERROR 10103"); ErrorLogging newLogger = new ErrorLogging("10103"); Thread errorThread = new

I'm having a weird problem with my program. I'm developing a windows form application. When I debug it through Visual Studio (F5) it works perfectly correctly, but when I run its executable it crashes and gives me "An unhandled exception of type 'System.ObjectDisposedException' occurred in mscorlib.dll". I tried to put a top level (on my outermost function) try/catch for catching this exception, but still the program crashes. What am I missing here? I didn't upload the code because I had to upload the whole code for you to see where the problem is. Wow, an ObjectDisposedException that isn't

I am using a .NET 4 SerialPort object to talk to a device attached to COM1. When I am done with the device, I call Close on the SerialPort. I do not call Dispose, but I believe that Close and Dispose are synonymous here. Usually this works just fine. Sometimes, however, I get the following exception some time later (The times I've seen range from 5 ms to 175 ms): System.ObjectDisposedException: Safe handle has been closed at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean& success) at System.StubHelpers.StubHelpers.SafeHandleAddRef(SafeHandle pHandle, Boolean& success) at

I've actually written a tracelistener component that logs to a networkstream. The code for that is here: using Newtonsoft.Json.Linq; using System; using System.Collections.Generic; using System.IO; using System.Linq; using System.Net.Sockets; using System.Text; using System.Threading.Tasks; namespace System.Diagnostics { public class NetworkStreamWriterTraceListener : DelimitedListTraceListener { NetworkStream _stream; StreamWriter _writer; StreamReader _reader; TcpClient client; bool IsDisposed = false; private NetworkStream GetStream(string configJson) { JObject config = JObject.Parse

When implementing IDisposable, I undertand that every method that shouldn't be called after the object's been disposed should throw the ObjectDisposedException . But what is the standard for the name object that should be passed to the exception's constructor? I believe the recommended practice is to throw the following: throw new ObjectDisposedException(GetType().FullName); Or including the check, these two lines of code at the top of each method that needs it (obviously not the Dispose method itself): if (this.disposed) throw new ObjectDisposedException(GetType().FullName); Might even be

I'm building a 4 layered ASP.Net web application. The layers are: Data Layer Entity Layer Business Layer UI Layer The entity layer has my data model classes and is built from my entity data model (edmx file) in the datalayer using T4 templates (POCO). The entity layer is referenced in all other layers. My data layer has a class called SourceKeyRepository which has a function like so: public IEnumerable<SourceKey> Get(SourceKey sk) { using (dmc = new DataModelContainer()) { var query = from SourceKey in dmc.SourceKeys select SourceKey; if (sk.sourceKey1 != null) { query = from SourceKey in

I create a MemoryStream , pass it to CryptoStream for writing. I want the CryptoStream to encrypt, and leave the MemoryStream open for me to then read into something else. But as soon as CryptoStream is disposed, it disposes of MemoryStream too. Can CryptoStream leave the base MemoryStream open somehow? using (MemoryStream scratch = new MemoryStream()) { using (AesManaged aes = new AesManaged()) { // <snip> // Set some aes parameters, including Key, IV, etc. // </snip> ICryptoTransform encryptor = aes.CreateEncryptor(); using (CryptoStream myCryptoStream = new CryptoStream(scratch, encryptor,