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
GitHub or Developer Community 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 924 [details]
The MSDN documentation for System.Xml.Linq.Extensions.Remove() (http://msdn.microsoft.com/en-us/library/bb357554(v=VS.90).aspx) has the following in the remarks section:
"This method uses snapshot semantics—that is, it copies the nodes in the source collection to a List<T> before disconnecting them from their parents. This is required to avoid issues with mixed imperative/declarative code."
However, Mono's version does not take similar precautions which can lead to the enumerator being placed in an inconsistent state. This is especially noticeable when using NodesBeforeSelf() and NodesAfterSelf().
The attached code fragment demonstrates the issue.
That's a good catch. Fixed in git master df47a23. Thanks for the report.