Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
When closing MonoDevelop 3.0 on Windows, I sometimes get this crash. It seems to be caused by the Android designer, as I don't get it if I don't open the designer:
System.ObjectDisposedException was unhandled
Message=Cannot access a closed file.
at System.IO.FileStream.Write(Byte array, Int32 offset, Int32 count)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.StreamWriter.Write(Char buffer, Int32 index, Int32 count)
at MonoDevelop.Core.ProgressMonitoring.LogTextWriter.Write(Char buffer, Int32 index, Int32 count)
at System.IO.TextWriter.WriteLine(String value)
at System.IO.TextWriter.SyncTextWriter.WriteLine(String value)
at Cairo.Context.Dispose(Boolean disposing)
I might have but I'm on holiday and not near my Mac. However: please, please have a look at the code and maybe you see some issue. I need progress on this. At the moment I don't even know WHAT object gets disposed. And worse: Mono doesn't recover! I will be back on Monday trying to get you a testcase but I'd prefer to have some results by then already because this is putting my project on ice.
Rene, the above crash is a MonoDevelop bug, not sure how this puts your project on ice.
Did you comment on the wrong post?
Yeah. Wrong bug. I wanted to comment #5904
The android designer has been rewritten ever since, so I guess we can safely close this issue due to lack of activity.