Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
x/mobile/app: SIGABRT during (*asset).close #10949
The following panic is reproducible from drummachine's stop handler.
Are there any other logs? For example, a fatal log before it?
This may simply be the OS deciding the process has taken too long. In which case we could register a signal handler listening for SIGABRT following a stop and not bother printing a stack trace. Or it could be a LOG_FATAL somewhere due to some misused API. It is hard to tell from just this.
I see a fatal log from libc.
Could it be why the asset pointer being a dangling pointer? If you can't reproduce, I will try to investigate it further when I have time.