Skip to content
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 by runDevicesPeriodicPing. #167

Closed
jiangjun1989 opened this issue Sep 12, 2023 · 1 comment
Closed

Crash by runDevicesPeriodicPing. #167

jiangjun1989 opened this issue Sep 12, 2023 · 1 comment
Labels
question Further information is requested

Comments

@jiangjun1989
Copy link

pid: 25915, tid: 26319, name: DefaultDispatch >>> com.matter.test <<<
2023-09-12 14:50:57.503 DEBUG pid-26650 A #1 pc 000000000087a934 /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk
2023-09-12 14:50:57.503 DEBUG pid-26650 A #2 pc 00000000017d95a0 /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk
2023-09-12 14:50:57.503 DEBUG pid-26650 A #3 pc 00000000017b82d4 /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk
2023-09-12 14:50:57.503 DEBUG pid-26650 A #4 pc 00000000017b7ae8 /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk
2023-09-12 14:50:57.503 DEBUG pid-26650 A #5 pc 00000000017456f0 /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk
2023-09-12 14:50:57.503 DEBUG pid-26650 A #6 pc 0000000001775824 /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk (chip::OperationalSessionSetup::DequeueConnectionCallbacks(chip::ChipError)+640)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #7 pc 0000000001775334 /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk (chip::OperationalSessionSetup::Connect(chip::Callback::Callback<void ()(void, chip::Messaging::ExchangeManager&, chip::SessionHandle const&)>, chip::Callback::Callback<void ()(void*, chip::ScopedNodeId const&, chip::ChipError)>)+616)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #8 pc 0000000001745204 /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk
2023-09-12 14:50:57.503 DEBUG pid-26650 A #9 pc 0000000000897500 /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk (chip::Controller::DeviceController::GetConnectedDevice(unsigned long, chip::Callback::Callback<void (
)(void*, chip::Messaging::ExchangeManager&, chip::SessionHandle const&)>, chip::Callback::Callback<void ()(void*, chip::ScopedNodeId const&, chip::ChipError)>*)+176)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #10 pc 00000000008973a4 /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk (Java_chip_devicecontroller_ChipDeviceController_getConnectedDevicePointer+200)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #13 pc 000000000033e5fe [anon:dalvik-classes.dex extracted in memory from /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk] (chip.devicecontroller.ChipDeviceController.getConnectedDevicePointer+26)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #15 pc 00000000000180d6 /data/data/com.matter.test/code_cache/.overlay/base.apk/classes28.dex (com.matter.test.matter.chip.ChipClient.getConnectedDevicePointer+50)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #17 pc 000000000001c1c8 /data/data/com.matter.test/code_cache/.overlay/base.apk/classes28.dex (com.matter.test.matter.chip.ClustersHelper.getDeviceStateOnOffCluster+184)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #19 pc 000000000009ea0e /data/data/com.matter.test/code_cache/.overlay/base.apk/classes24.dex (com.matter.test.v2.util.MeshControlUtil$runDevicesPeriodicPing$1.invokeSuspend+478)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #21 pc 00000000001ffefe [anon:dalvik-classes32.dex extracted in memory from /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk!classes32.dex] (kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith+42)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #24 pc 000000000027b33e [anon:dalvik-classes32.dex extracted in memory from /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk!classes32.dex] (kotlinx.coroutines.internal.LimitedDispatcher.run+26)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #26 pc 0000000000282d06 [anon:dalvik-classes32.dex extracted in memory from /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk!classes32.dex] (kotlinx.coroutines.scheduling.TaskImpl.run+6)
2023-09-12 14:50:57.503 DEBUG pid-26650 A #28 pc 0000000000281e1e [anon:dalvik-classes32.dex extracted in memory from /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk!classes32.dex] (kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely+2)
2023-09-12 14:50:57.504 DEBUG pid-26650 A #30 pc 0000000000280b3a [anon:dalvik-classes32.dex extracted in memory from /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk!classes32.dex] (kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask+34)
2023-09-12 14:50:57.504 DEBUG pid-26650 A #32 pc 0000000000280c68 [anon:dalvik-classes32.dex extracted in memory from /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk!classes32.dex] (kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker+56)
2023-09-12 14:50:57.504 DEBUG pid-26650 A #34 pc 0000000000280c18 [anon:dalvik-classes32.dex extracted in memory from /data/app/~~EspAOHjDYQwcyV-l8A0xUg==/com.matter.test-C0tb2CyYtq3eMt8lYnFrMw==/base.apk!classes32.dex] (kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run+0)

@pierredelisle
Copy link
Contributor

Is this using GHSAFM?
Could you provide the full logs from the phone?
See https://github.com/google-home/sample-apps-for-matter-android/wiki/How-to-investigate-issues-with-GHSAFM%E2%80%903p%E2%80%90ecosystem.

@pierredelisle pierredelisle added the question Further information is requested label Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants