-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
crash at json::destroy on android #1812
Comments
here is another crash stacktrace
here is my code:
|
If you remove the 'std::move' does it still crash? That might give a hint at what is going on. |
I'll try |
U can try to make a forever looop in a buggy code places and check if it crashes and how often. (Probably even 1-10hours test might show something))) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@zhaohuaxishi this is pure speculation, but I've seen something very similar before. I've seen similar callstacks on mobile projects. They can appear to come from libraries like this one that use a lot of standard library features (particularly strings and locale related stuff). But the root cause is another thread is just shutting down at the same time. You should make sure that all threads are terminated before shutting down, and that asio will not spin up any more working threads. |
@djewsbury thank you very much for help, this seems to be a resonable explanation. how could i make sure that all threads are terminated before shutting down. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I got this crash stacktrace from bugly(something like crashlytics) report,it seems that json::destroy will crash some times. I can not reproduce this crash and have no more information.
Is there same other way to find out what cause this crash?
The text was updated successfully, but these errors were encountered: