Closed cihadturhan closed 3 weeks ago
- It would be helpful to have a full, unfiltered logcat in txt format
Unfortunately, the reports are from Google play and it doesn’t show any logs afaik.
- Is it reproducible in a new project running only the capture from screen demo project?
I didn’t see any issues on my device and I can’t share demo project with those users.
- Are both phones definitely Android 13?
- Is it occurring on any other devices?
Here is the report:
OK, that's not a huge amount to go on. The dev team is on annual leave at the moment, so we'll review this when they get back.
OK, that's not a huge amount to go on. The dev team is on annual leave at the moment, so we'll review this when they get back.
Thanks, meanwhile I'm talking to some of the users. If I find something concrete I will share it.
I'm going to close this for now as we don't have enough information to go on. Please feel free to reopen when you can reproduce it.
I integrated two different crash reporting libraries but none of them gave meaningful info because the crash occurs in low-level code.
Just recently I integrated firebase and uploaded sourcemaps and this is the call stack
Example one:
null pointer dereference: SIGABRT 0x0000000000000000
#00 pc 0x9ce10 libc.so (BuildId: f5f7a5dceb6ab17a1a448521eb52ce18)
#01 pc 0x9cde0 libc.so (BuildId: f5f7a5dceb6ab17a1a448521eb52ce18)
#02 pc 0x92ffd0 libart.so (BuildId: 3b4ed3e67a9a04e3a37d259cd59da05b)
#03 pc 0x160fc libbase.so (BuildId: 42d41ca7c77853791d096606e7186547)
#04 pc 0x7060 liblog.so (BuildId: 0f997d9aa97b9075a420958a903b4ccb)
#05 pc 0x101a8 libutils.so (BuildId: 267ba2041a69a401110f388720a8e47b)
#06 pc 0x264bc libmediandk.so (BuildId: 43850a88a1298d82672f78da7018d9ef)
#07 pc 0x838ec libAVProMovieCaptureNative.so (BuildId: a3cae5fa030a0d8d0d1eb78a6cfb2e6c58e2a8c1)
#08 pc 0x85c74 libAVProMovieCaptureNative.so (BuildId: a3cae5fa030a0d8d0d1eb78a6cfb2e6c58e2a8c1)
#09 pc 0x104fe4 libc.so (BuildId: f5f7a5dceb6ab17a1a448521eb52ce18)
#10 pc 0x9e77c libc.so (BuildId: f5f7a5dceb6ab17a1a448521eb52ce18)
Any idea why I can't see the detailed logs on firebase although I uploaded symbols? Is this because your your prebuilt binary don't have symbols?
Another crash report:
Crashed: Thread: SIGSEGV 0x000000726c943000
#00 pc 0x852e8 libc.so (BuildId: 351225fa1d718acf9e00214d7dd5d405)
#01 pc 0x828dc libAVProMovieCaptureNative.so (BuildId: a3cae5fa030a0d8d0d1eb78a6cfb2e6c58e2a8c1)
#02 pc 0x825d8 libAVProMovieCaptureNative.so (BuildId: a3cae5fa030a0d8d0d1eb78a6cfb2e6c58e2a8c1)
#03 pc 0x85c74 libAVProMovieCaptureNative.so (BuildId: a3cae5fa030a0d8d0d1eb78a6cfb2e6c58e2a8c1)
#04 pc 0xeb5c0 libc.so (BuildId: 351225fa1d718acf9e00214d7dd5d405)
#05 pc 0x8ae78 libc.so (BuildId: 351225fa1d718acf9e00214d7dd5d405)
I'm going to close this for now as we don't have enough information to go on. Please feel free to reopen when you can reproduce it.
Hello, I finally understood the problem. The problem was something different than I thought.
During recording on Android (maybe also on iOS too)
https://github.com/user-attachments/assets/edd69267-81b9-4e94-b9d0-62817406eb48
GameObject
with DontDestroyOnLoad
so it never gets destroyed unexpectedly?
b. A local GameObject
but it should stop the recording immediately when it gets destroyed?background
?I will still implement my workaround, but could you reopen the issue and fix this crash on your end as well?
Forgot to ping you @Chris-RH @AndrewRH @MorrisRH
Are you able to provide the logcat in txt format please? that's pretty difficult to parse as it is
Are you able to provide the logcat in txt format please? that's pretty difficult to parse as it is
Hi @Chris-RH, I disabled scene switching when there is recording on progress and it reduced crashes drastically.
However, there are still some crashes happening from FMOD, I wonder if you use FMOD in any of the stages.
[libunity.so] FMOD::DSPPitchShift::resetCallback(FMOD_DSP_STATE*)
Sample attributes:
[motorola cancunf (moto g54 5G)](https://play.google.com/console/u/0/developers/4940193866272130552/app/4973866357303823618/vitals/crashes/dd6b62044d45a046385621b2078242ab/details?days=28&versionCode=157&isUserPerceived=true#)
[Android 14 (SDK 34)](https://play.google.com/console/u/0/developers/4940193866272130552/app/4973866357303823618/vitals/crashes/dd6b62044d45a046385621b2078242ab/details?days=28&versionCode=157&isUserPerceived=true#)
Version: 157 (2.1.1)Occurred: 2 hours ago
Game engine build fingerprint:
2022.3.22f1;IL2CPP;Release;StripEngineCode:1;OptimizedFramePacing:1;
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 19960 >>> com.creativetechnology.beatbounce <<<
backtrace:
#00 pc 0x000000000008cf84 /apex/com.android.runtime/lib64/bionic/libc.so (memset+196)
#01 pc 0x0000000000f0d4d0 /data/app/~~6QeDsGmzyIWjrxKbqIVbGQ==/com.creativetechnology.beatbounce-ZA0Bgj81oT6m0ST9R3XNtA==/lib/arm64/libunity.so
Hi @cihadturhan
We don't use FMOD in any of the stages.
I'm going to close this one now. If you find anything AVPro specific, please get back to us :)
Unity Version
2022.3.22f1
AVPro Movie Capture Version
5.3.0-MOBILE
Which platform(s) are you using?
iOS, Android
Which OS version(s) are you using?
Android 13
Which rendering API(s) are you using?
Vulkan
Hardware
POCO gust (POCO C65) OnePlus6T (OnePlus6T)
Which capture component are you using?
Capture From Screen
Capture mode
Realtime
Which output mode are you using?
Video file
Video codecs
H264
Audio source
None
Audio codecs
AAC
Any other component configuration
No response
The issue
Hi, I've got multiple reports on some android devices crashes. Game engine build fingerprint: 2022.3.22f1;IL2CPP;Release;StripEngineCode:1;OptimizedFramePacing:1;
Log output
Crash 2
Crash 3