Try to find the reason for a weird runtime crash #3796
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
grendello
added
do-not-merge
grendello
changed the title
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
grendello
force-pushed
the
dlopen-logging
branch
2 times, most recently
from
f80c9bb to
32ad3f4
Compare
Contributor
Author
|
/azp run |
3 similar comments
Contributor
Author
|
/azp run |
Contributor
Author
|
/azp run |
Contributor
Author
|
/azp run |
grendello
force-pushed
the
dlopen-logging
branch
from
4cc1e95 to
a51c649
Compare
Contributor
Author
|
/azp run |
1 similar comment
Contributor
Author
|
/azp run |
The crash is: 10-15 14:25:04.854 3342 3342 E mono : 10-15 14:25:04.854 3342 3342 E mono : Unhandled Exception: 10-15 14:25:04.854 3342 3342 E mono : System.DllNotFoundException: __Internal assembly:<unknown assembly> type:<unknown type> member:(null) 10-15 14:25:04.854 3342 3342 E mono : at (wrapper managed-to-native) Android.Runtime.JNIEnv.monodroid_timing_start(string) 10-15 14:25:04.854 3342 3342 E mono : at Android.Runtime.JNIEnv.Initialize (Android.Runtime.JnienvInitializeArgs* args) [0x0001c] in <1260048817b5414c97481e16c94f6621>:0 It's one of those cases that are "impossible", try to find out how possible is the impossible
grendello
force-pushed
the
dlopen-logging
branch
from
a51c649 to
c36b724
Compare
Contributor
Author
|
/azp run |
See if embedded DSO mode is enabled - it should be, but sometimes it appears as if it isn't set and thus we get invalid paths where to look for our DSOs
jonpryor
pushed a commit
that referenced
this pull request
Nov 12, 2019
Context: 6d85759 Context: #3796 Context: 6d85759#diff-e99739c16155208685952aa52870d4cdL33-L39 When switching from C-style `xcalloc()` to C++-style `new` I failed to use the proper type to allocate the array which holds directories where Android placed the `.apk` files of the application. This mistake manifested itself only when using AppBundles, which is where we allocate more than one entry of the array. The resulting error was the following runtime exception: Unhandled Exception: System.DllNotFoundException: __Internal assembly:<unknown assembly> type:<unknown type> member:(null) at (wrapper managed-to-native) Android.Runtime.JNIEnv.monodroid_timing_start(string) which occurred because the Xamarin.Android runtime failed to load `libmonodroid.so` from one of the directories that should have been stored in the array mentioned above - usually found in the *last* entry of the array. When iterating over the array, the XA runtime would end up with a null pointer after the end of the array instead of a pointer to the last entry. This commit uses the proper type when allocating the array.
jonpryor
pushed a commit
that referenced
this pull request
Nov 12, 2019
Context: 6d85759 Context: #3796 Context: 6d85759#diff-e99739c16155208685952aa52870d4cdL33-L39 When switching from C-style `xcalloc()` to C++-style `new` I failed to use the proper type to allocate the array which holds directories where Android placed the `.apk` files of the application. This mistake manifested itself only when using AppBundles, which is where we allocate more than one entry of the array. The resulting error was the following runtime exception: Unhandled Exception: System.DllNotFoundException: __Internal assembly:<unknown assembly> type:<unknown type> member:(null) at (wrapper managed-to-native) Android.Runtime.JNIEnv.monodroid_timing_start(string) which occurred because the Xamarin.Android runtime failed to load `libmonodroid.so` from one of the directories that should have been stored in the array mentioned above - usually found in the *last* entry of the array. When iterating over the array, the XA runtime would end up with a null pointer after the end of the array instead of a pointer to the last entry. This commit uses the proper type when allocating the array.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The crash is:
It's one of those cases that are "impossible", try to find out how possible is
the impossible