Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flaky runtime.finalizer-exception.exe (Assertion at unwind.c:640, condition `cfa_reg != -1' not met) #9566

Closed
jaykrell opened this issue Jul 14, 2018 · 8 comments · Fixed by #10149
Assignees
Projects

Comments

@jaykrell
Copy link
Collaborator

@jaykrell jaykrell commented Jul 14, 2018

Steps to Reproduce

  1. Submit a PR.

Current Behavior

Failures, for example:

https://jenkins.mono-project.com/job/test-mono-pull-request-arm64/11720/

MonoTests.runtime.finalizer-exception.exe

https://jenkins.mono-project.com/job/test-mono-pull-request-arm64/11720/testReport/junit/MonoTests/runtime/finalizer_exception_exe/

Failing for the past 1 build (Since Unstable#11720 )
Took 0.38 sec.
add description
Stacktrace
                                                MESSAGE:
                                                caught
* Assertion at unwind.c:640, condition `cfa_reg != -1' not met

* Assertion at mini-exceptions.c:1191, condition `unwind_options == MONO_UNWIND_NONE' not met

                                                +++++++++++++++++++
                                                STACK TRACE:
                                                Stacktrace:

For this we probably could use some EH stress that forces
an exception at every instruction or every call, or every call and dereference.

Expected Behavior

Success.

@jaykrell

This comment has been minimized.

@lewurm lewurm added this to Bugs Pool in Bugs Week via automation Jul 16, 2018
jaykrell added a commit that referenced this issue Aug 15, 2018
… correct, i.e. no nesting

mono_thread_info_set_is_async_context assert that setting to false is correct, i.e. no nesting
Possibly related to #9566
@BrzVlad BrzVlad moved this from Bugs Pool to In Progress in Bugs Week Aug 15, 2018
@BrzVlad BrzVlad self-assigned this Aug 15, 2018
BrzVlad added a commit to BrzVlad/mono that referenced this issue Aug 16, 2018
BrzVlad added a commit to BrzVlad/mono that referenced this issue Aug 17, 2018
Bugs Week automation moved this from In Progress to Done Aug 20, 2018
BrzVlad added a commit that referenced this issue Aug 20, 2018
Fixes #9566
@marek-safar marek-safar moved this from Done to Archived in Bugs Week Sep 24, 2018
@DaanTacoSchool

This comment has been minimized.

Copy link

@DaanTacoSchool DaanTacoSchool commented Nov 30, 2018

not a 100% sure this is the correct thread, but the error in the title still appears. i can find a lot about it in unity threads, but for me it occurs in VS2017 w/ Xamarin forms. in the android emulator. see the link for details

@BrzVlad

This comment has been minimized.

Copy link
Member

@BrzVlad BrzVlad commented Dec 4, 2018

@DaanTacoSchool This error is not really actionable from the assertion only, we would need a reproduction case. In the meantime, for the next release, I'll include additional logging when this error shows so we can hopefully debug it more easily.

@DaanTacoSchool

This comment has been minimized.

Copy link

@DaanTacoSchool DaanTacoSchool commented Dec 4, 2018

@DaanTacoSchool

This comment has been minimized.

Copy link

@DaanTacoSchool DaanTacoSchool commented Dec 7, 2018

@BrzVlad I narrowed down the cause to a method in the REST service implementation. To be more specific the following line;
oc = JsonConvert.DeserializeObject<ObservableCollection<T>>(content);

This is wierd as this line hasnt changed for the last months. it throws the following error without native stacktrace;
* Assertion at /Users/builder/jenkins/workspace/xamarin-android-d15-9/xamarin-android/external/mono/mono/mini/unwind.c:640, condition cfa_reg != -1' not met`

The JsonConvert method is from the newtonsoft.json niuget package. which i guess internally calls the mono assert. i will try to find out if this is the case.

@DaanTacoSchool

This comment has been minimized.

Copy link

@DaanTacoSchool DaanTacoSchool commented Dec 7, 2018

posted it on SO too here

@jaykrell

This comment has been minimized.

Copy link
Collaborator Author

@jaykrell jaykrell commented Dec 7, 2018

But is it fixed by?
bbd6a6a
?
What version are you running?

@DaanTacoSchool

This comment has been minimized.

Copy link

@DaanTacoSchool DaanTacoSchool commented Dec 7, 2018

@jaykrell the reference in the android project says Runtime version v4.0.30319 (the dotnet version its compiled against) the version field (version of reference) shows as 0.0.0.0 and the xamarin forms dependency (in root proj.) is 3.0.0.561731

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Bugs Week
Archived
4 participants
You can’t perform that action at this time.