Crash problem of Chrome browser

background

The test reported GMS On the version Chrome Browser play youtube video , Go straight back crash.

  Enclosed Chrome Stack information printed by browser error , There are still many similar ones on the Internet bug, However, sometimes specific cases need specific analysis . Basically, I only know ThreadPoolSingl This thread triggers , But why did it happen ？

And further found a problem is , here camera app It can't be opened , For the time being, there is no way to understand the relationship between the two .

06-01 10:47:46.584  1325  1412 I chatty  : uid=1000(system) ActivityManager expire 7 lines
06-01 10:47:47.107  1325  1462 I chatty  : uid=1000(system) batterystats-wo expire 10 lines
06-01 10:47:51.456  1325  7132 I chatty  : uid=1000(system) Binder:1325_15 expire 2 lines
06-01 10:47:53.442  1325  9253 I chatty  : uid=1000(system) Binder:1325_1A expire 3 lines
06-01 10:47:53.679  1325  1325 I chatty  : uid=1000 system_server expire 2 lines
06-01 10:47:53.986  9259  9328 F libc    : Fatal signal 5 (SIGTRAP), code -6 (SI_TKILL) in tid 9328 (ThreadPoolSingl), pid 9259 (.android.chrome)
06-01 10:47:54.198 10220 10220 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-01 10:47:54.198 10220 10220 F DEBUG   : Build fingerprint: 'xxx/xxx/xxx-1:10/QKQ1.200407.002/217.01.00.0031:user/release-keys'
06-01 10:47:54.198 10220 10220 F DEBUG   : Revision: 'sdm450'
06-01 10:47:54.198 10220 10220 F DEBUG   : ABI: 'arm'
06-01 10:47:54.199 10220 10220 F DEBUG   : Timestamp: 2022-06-01 10:47:54+0800
06-01 10:47:54.199 10220 10220 F DEBUG   : pid: 9259, tid: 9328, name: ThreadPoolSingl  >>> com.android.chrome <<<
06-01 10:47:54.199 10220 10220 F DEBUG   : uid: 10139
06-01 10:47:54.199 10220 10220 F DEBUG   : signal 5 (SIGTRAP), code -6 (SI_TKILL), fault addr --------
06-01 10:47:54.199 10220 10220 F DEBUG   : Abort message: '[FATAL:jni_android.cc(249)] Please include Java exception stack in crash report
06-01 10:47:54.199 10220 10220 F DEBUG   : '
06-01 10:47:54.199 10220 10220 F DEBUG   :     r0  00000000  r1  00000000  r2  7fffffff  r3  00000000
06-01 10:47:54.199 10220 10220 F DEBUG   :     r4  bb0e442c  r5  0000004f  r6  aa993320  r7  0000004f
06-01 10:47:54.199 10220 10220 F DEBUG   :     r8  bb0e4878  r9  bb0e487c  r10 e928f260  r11 bb0e442c
06-01 10:47:54.199 10220 10220 F DEBUG   :     ip  bb0e43f0  sp  bb0e4418  lr  e927dfc3  pc  a948ec74
06-01 10:47:54.201 10220 10220 F DEBUG   : 
06-01 10:47:54.201 10220 10220 F DEBUG   : backtrace:
06-01 10:47:54.201 10220 10220 F DEBUG   :       #00 pc 01c8dc74  /system/product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome.so (offset 0x665000) (BuildId: 2e75332e045e71dbc9a5c7b8964276faac6e441d)

Continue from log Middle tracking , Found some ThreadPoolSingl Thread initiated read camera Attribute selinux jurisdiction Log

06-01 10:51:26.455 13271 13271 W ThreadPoolSingl: type=1400 audit(0.0:473): avc: denied { read } for name="u:object_r:persist_camera_prop:s0" dev="tmpfs" ino=15713 scontext=u:r:untrusted_app:s0:c139,c256,c512,c768 tcontext=u:object_r:persist_camera_prop:s0 tclass=file permissive=0
06-01 10:51:26.455 13271 13271 I chatty  : uid=10139(com.android.chrome) identical 1 line
06-01 10:51:26.455 13271 13271 W ThreadPoolSingl: type=1400 audit(0.0:475): avc: denied { read } for name="u:object_r:persist_camera_prop:s0" dev="tmpfs" ino=15713 scontext=u:r:untrusted_app:s0:c139,c256,c512,c768 tcontext=u:object_r:persist_camera_prop:s0 tclass=file permissive=0
06-01 10:51:26.473 13271 13352 E libc    : Access denied finding property "vendor.camera.aux.packagelist"
06-01 10:51:26.474 13271 13352 I chatty  : uid=10139(com.android.chrome) identical 1 line
06-01 10:51:26.474 13271 13352 E libc    : Access denied finding property "vendor.camera.aux.packagelist"
06-01 10:51:26.483   815  1770 W ServiceManager: Permission failure: android.permission.CAMERA from uid=10139 pid=13271
06-01 10:51:26.465 13271 13271 W ThreadPoolSingl: type=1400 audit(0.0:476): avc: denied { read } for name="u:object_r:persist_camera_prop:s0" dev="tmpfs" ino=15713 scontext=u:r:untrusted_app:s0:c139,c256,c512,c768 tcontext=u:object_r:persist_camera_prop:s0 tclass=file permissive=0
06-01 10:51:26.484 13271 13352 E libc    : Access denied finding property "vendor.camera.aux.packagelist"

in addition , Also through decompilation chrome browser apk, It is found that there are some functions similar to scanning QR code , Need to call camera, The main sign is attributes like this vendor.camera.aux.packagelist It's true chrome Search in the browser .

Simply locate here , I began to suspect that it was a single machine camera There is a problem with the hardware , Therefore, the doubts that the previously reserved site did not dare to restart and restore the factory are basically much smaller

Try to restart , The phenomenon still exists ;

Return to factory , The phenomenon still exists .

Then start the final step of verification ,

Directly exchange with the machine without problems camera module , The result is such an unexpected confirmation , Changed camera after ,camera Can open the , Browser play youtube It's normal too. . And the problem of perfect recurrence of the exchanged machine .

thus , This problem is over , Think back a little , Now let's look at , It is not particularly difficult to analyze , But if it has been in the initial chrome Just play youtube Just crash Click to analyze and locate , It's really not so smooth ; There happened to be a camera Problems that can't be solved , It is equivalent to giving a clear direction .

Have a problem , How to check , Feel that confirming the effective direction still has a great impact on the efficiency of solving a problem , But sometimes you need to make a detour , After all, I will let myself dig deeper into more knowledge points I didn't want to touch before .