https://bugzilla.novell.com/show_bug.cgi?id=663259
https://bugzilla.novell.com/show_bug.cgi?id=663259#c2 --- Comment #2 from Sebastien Pouliot <[email protected]> 2011-01-10 13:05:38 UTC --- so I had to sleep over it ;-) As far as I can tell it's not a bug in the rule itself. The generated code includes a lot of small while-loops in the catch handler. This makes the number possible code paths *extremely* high (so it looks like an infinite loop). Solutions, easy to hard, are: a) stop analyzing after reaching more than X paths; b) reduce the memory requirement of the code paths; c) make the "code paths" more intelligent since the while-loop could be flattened; The best solution would be all of them - but it will likely be only (a) for 2.10. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
