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 for Bug 29556 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The GetSchema(string) function calls GetSchema(string, string) which in turn checks if the connection is closed (in which case it throws an exception), but otherwise it simply calls itself with the same initial arguments. Attempting to wait out the database timeout perhaps? Or simply trying to blow up system memory? In either case, it's horrible code and should be fixed. If the function is incomplete, it should throw a NotImplemented exception instead of wasting system resources and relying on the VM to eventually detect it and kill it. According to the mono class status page, it appears that System.Data.OdbcConnection.GetSchema is good to go! I suspect at least throwing an exception would potentially flag it correctly in those docs and save people like myself a lot of time.
I don't know how long this has been a problem, but I suspect a very long time. I have tested with 3.10 and 3.12 with the same results.
This is still an issue in version 4.0.1 making any GetSchema calls to ODBC sources not only unusable, but catastrophic to the running program. Does anyone look at these bugs? Are more devs needed to address the open bugs?