-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Parse causing crash on android. Cannot catch. #2021
Comments
Do you have more information like a stack trace or example code including the input. Did you try to run the code with address sanitizer enabled or using Valgrind? |
Hi, we managed to isolate the json out of the crash. Something is happening at the same time as the json call and ruining the memory. Sorry for wasting time! |
Hi how did you manage to resolve this issue? I am experiencing same issue on IOS. App crash is happening on specific network while parsing JSON. Exception not caught. Not entering in rescue block as well. |
@YaminiT-94 The information was being sent via udp and being received and sent down to c++ through jni. Once the data was processed it was sent off via an internal messaging system and then the local variables were deleted. There was an extra delete of a variable that just happened to always happen at the same time as the json data getting parsed as they were being executed on different threads. Basically it was completely unrelated to the json and had to do with an extra delete causing a crash. |
Hi, in my case application is crashing due to.poor network. In watchdog crash report I received excpetionas below: Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d Termination Description: SPRINGBOARD, scene-update As given solution in Apple documentation I cannot convert that synchronous call to asynchronous, neither can put on secondary thread. No use of increasing network timeout. Watchdog timeout is less than network timeout. Any suggesstion/solution on this? |
Running and android app on android 10. Sometimes, when using nlohmann::json::parse my application will crash. I am parsing simple strings like {"stringy":{"value":"a string"}}. Sometimes it works and I can use the resulting object. Mostly it crashes with the error:
0xebadde09 skipped times: 0
A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x227245ef88a0 ...
A try catch block will not help at all. It doesn't catch anything. The log message before the parse prints and then the app crashes immediately.
I know there is some information about 0xebadde09 being related to hardware acceleration but I have disabled that as well (this is running in a background service anyway). Any hints on what to do or where to look would be appreciated. I've been trying many permutations with no luck.
nlohmann::json::parse a valid std::string.
Successful parse
Crash
Using android studio with the -std=c++11 flag set.
develop
branch?Released 3.6.1 and 3.7.3
N/A
The text was updated successfully, but these errors were encountered: