tuningfork
tuningfork copied to clipboard
android
Crash with using Performance Tuner
We are using APT version 1.5.0.60b0ddc9 Unity 2021.3.26f1 and see a lot of crashes coming from the plugin
null pointer dereference: SIGSEGV 0x0000000000000018 #00 pc 0x2d350 libunitytuningfork.so (BuildId: 04852f825bd5553cd874f1a06c85fd27ef52a1b5) #01 pc 0x2d348 libunitytuningfork.so (BuildId: 04852f825bd5553cd874f1a06c85fd27ef52a1b5) #02 pc 0x27ae0 libunitytuningfork.so (BuildId: 04852f825bd5553cd874f1a06c85fd27ef52a1b5) #03 pc 0x3460c libunitytuningfork.so (BuildId: 04852f825bd5553cd874f1a06c85fd27ef52a1b5) #04 pc 0x347b8 libunitytuningfork.so (BuildId: 04852f825bd5553cd874f1a06c85fd27ef52a1b5) #05 pc 0xb6668 libc.so (BuildId: 3e3c5ec517682e9d3afdceafc14d447f) #06 pc 0x532cc libc.so (BuildId: 3e3c5ec517682e9d3afdceafc14d447f)
null pointer dereference: SIGSEGV 0x0000000000000018 #00 pc 0x2d350 libunitytuningfork.so (BuildId: 04852f825bd5553cd874f1a06c85fd27ef52a1b5) #01 pc 0x2d348 libunitytuningfork.so (BuildId: 04852f825bd5553cd874f1a06c85fd27ef52a1b5) #02 pc 0x27ae0 libunitytuningfork.so (BuildId: 04852f825bd5553cd874f1a06c85fd27ef52a1b5) #03 pc 0x3460c libunitytuningfork.so (BuildId: 04852f825bd5553cd874f1a06c85fd27ef52a1b5) #04 pc 0x347b8 libunitytuningfork.so (BuildId: 04852f825bd5553cd874f1a06c85fd27ef52a1b5) #05 pc 0xfb04c libc.so (BuildId: 373b3a68831a2041a671a8c53f383df5) #06 pc 0x8e3b0 libc.so (BuildId: 373b3a68831a2041a671a8c53f383df5)
What can we do to fix it?
Hello Igor,
We'll need a bit more information to understand what really is going on here. Is there a chance you could provide us with an apk and specific instructions to reproduce? If not, at least a more detailed logcat information or a bugreport taken right after a crash would be appreciated as well.
Lastly, if you could move this issue to google's issue tracker through this link; https://issuetracker.google.com/issues/new?component=778598&template=1370784 we could more efficiently progress through this issue.
hello @labalov Unfortunately, we don't have steps to reproduce - it works ok on out devices
@IgorGalimski You'll get a better stacktrace if you upload debug symbols. Is this coming from the Google Play Console or another crash reporting tool? Is the crash from end-users or another context such as Firebase Test Lab or the Google Play Pre-Launch Report?
