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 3780 [details]
I've just gotten the assertion:
Assertion should not be reached in sgen-scan-object.h:109
I cannot paste the full trace here because I cannot use copy&paste in XS due to another bug. Sigh. I attached a screenshot of the stack trace.
Can you give us the solution to reproduce this bug?
Sorry, no. I was doing something stupid but I thought you might be interested in the assertion.
What I did was basically:
public class Bar()
public void ButtonClicked(object sender EventArgs args)
// Assign the method and as the action assign the same method again.
IntDelegateMethod = foo(1, foo);
// Have a delegate that wants an "int" as only parameter.
public Action<int> IntDelegateMethod;
// A method that can be assigned to IntDelegateMethod because the second parameter is optional.
public void foo(int anInt, Action actionCallback = null)
if(actionCallback != null) actionCallback();
This crashes also if you debug and break in foo() and hover the "actionCallback" parameter.
After all it was just a search&replace problem and is pretty stupid code, but anyway I don't understand why it would crash.
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.
Doesn't look like there's a test case coming.