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.
Created attachment 1726 [details]
Screenshots of the exceptions
Our organization are newly entered into the Mono Development. Thru the
website "http://mono-project.com/Main_Page" collected the prerequisites
required for the installation of Mono.
Our System hardware and software configuration:
Framework: .Net 4.0
OS: Windows 7 Ultimate Service Pack 1
RAM: 4 GB
Type: 64 Bit Operating System
IDE: Mono - 18.104.22.168 (stable release)
GTK# for .NET 2.12.10
While loading the .Net application into the Mono IDE after few seconds encountering "OutOfMemoryException". Not able to trace the reason for the error. Can you support us on the same to troubleshoot.
For more information please find attached screen shots of the exceptions.
Thanks & Regards,
Please provide a screencast of the problem, it is not clear what the problem is
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.