Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) #9462
Comments
vyacheslav-volkov
added
Area: App Runtime
|
Can you extract |
grendello
added
Area: Mono Runtime
|
Hi @grendello, thanks for the quick response, I have attached the file. |
dotnet-policy-service
bot
added
need-attention
|
I remembered there's another place in the application that crashes with the same error but with a different address and stack trace. It was commented out in the file I sent. I’ve uncommented it and uploaded a new file. Here’s the log of that error: |
|
The symbolicated backtrace suggests your application throws some exception and the runtime trips over it, for some reason (locations presented in the same order as frames in the backtrace): @vyacheslav-volkov if you are able to reproduce the segfault locally, please record it using the following commands from the VS developer prompt (or mac terminal): $ adb shell setprop debug.mono.log default,assembly,mono_log_level=debug,mono_log_mask=all
$ adb logcat -G 64M
$ adb logcat -c
# Start and crash the application here, wait 10s and then:
$ adb logcat -d > log.txtIn the resulting |
|
thanks @grendello, will check soon, could you please check the second log? |
|
The second backtrace symbolicates as follows: It's a different issue. This one makes me wonder if it's a case of the linker removing too much. |
|
do I need to create a new issue for the second case? @grendello I checked logs and I see a lot of different errors like this for different types: But this is just warnings, I don't see any real exceptions. |
|
@grendello, I tried several times on the emulator and the device and information about the real exception is not written to the log. Any other suggestions on how to catch the exception? |
|
@grendello I've roughly located where the error occurs, it's a standard OperationCanceledException. There are several try-catch blocks in the stack trace, and everything works fine in debug mode. However, in release mode, the native code cannot retrieve the stack trace and crashes, even though the application has no unhandled exceptions. How is this possible? |
|
@grendello I need your help to find the reason I can't release the app as it crashes frequently (same code on iOS NativeAOT works without any problem). if I ignore cancellationToken it will work, there is a try/catch in this code up the stack but even if I explicitly add it to the code it will fail: |
Android framework version
net8.0-android
Affected platform version
NET 8.0.403
Description
I'm encountering an error in my application, but only in the release build. In debug mode, the application works without any issues, but in the release build, I get an error at the same point during certain actions. Since the project is commercial, I cannot provide the specific code.
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x10008Steps to Reproduce
Run the application in release mode
Did you find any workaround?
No response
Relevant log output
update: the fault address is always the same
fault addr 0x10008The text was updated successfully, but these errors were encountered: