Can you please provide the crash id from chrome://crashes.

Do you have an URI that this reproduces on?

As I mentioned above, when trying to meet "http://weixin.qq.com/r/" scheme uri, Chrome crashed.

Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I've loaded that URI and it doesn't crash for me on a Nexus 5X. Are you able to provide the crash id?

First , you could install WeChat , and then load url "http://lijiajiahyp.cn/testwechat/", then click the link. 
On my device , Nexus 6, Android 6.0, Chrome and Chromium would crash.

The url should be an scheme intent to launch an activity of WeChat , not loaded in Chrome directly.

Would you be OK to test like above again?


The crash log is as follows:


[FATAL:jni_android.cc(236)] Please include Java exception stack in crash report
                                                               #00 0xa80f02ff /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x000832ff
                                                               #01 0xa80d603b /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x0006903b
                                                               #02 0x94221c63 /data/app/org.chromium.chrome-1/lib/arm/libchrome.cr.so+0x00369c63
                                                               #03 0x9445e8fb /data/app/org.chromium.chrome-1/lib/arm/libchrome.cr.so+0x005a68fb
                                                               #04 0x94221a57 /data/app/org.chromium.chrome-1/lib/arm/libchrome.cr.so+0x00369a57
                                                               #05 0x94221525 /data/app/org.chromium.chrome-1/lib/arm/libchrome.cr.so+0x00369525
                                                               #06 0xa80dff75 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x00072f75
                                                               #07 0xa80f615f /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x0008915f
                                                               #08 0xa80f62f9 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x000892f9
                                                               #09 0xa80f6469 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x00089469
                                                               #10 0xa80f7503 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x0008a503
                                                               #11 0x9f7d8d15 /data/app/org.chromium.chrome-1/oat/arm/base.odex+0x00e7ad15
                                                               
                                                               
                                                               
                                       --------- beginning of crash
07-26 09:55:19.656 14908-14908/org.chromium.chrome A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 14908 (chromium.chrome)

Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Dear,
Similar issue occured.
There are the logs as below.
Thanks.

<main.log>
08-18 17:11:56.032  7863  8349 I ActivityManager: START u0 {act=android.intent.action.VIEW cat=[android.intent.category.BROWSABLE] dat=intent://pay?tcode=6000001&mid=00035683&acode=6110002&callback=lotteapp/} from uid 10275 on display 0
...
08-18 17:11:56.269 16795 16795 F DEBUG   : backtrace:
08-18 17:11:56.269 16795 16795 F DEBUG   :     #00 pc 000000000006c074  /system/lib64/libc.so (tgkill+8)
08-18 17:11:56.270 16795 16795 F DEBUG   :     #01 pc 00000000000694f8  /system/lib64/libc.so (pthread_kill+64)
08-18 17:11:56.270 16795 16795 F DEBUG   :     #02 pc 0000000000024598  /system/lib64/libc.so (raise+24)
08-18 17:11:56.270 16795 16795 F DEBUG   :     #03 pc 000000000001cfb4  /system/lib64/libc.so (abort+52)
08-18 17:11:56.270 16795 16795 F DEBUG   :     #04 pc 0000000002db2d58  /data/app/com.android.chrome-1/base.apk (offset 0xdb6000)
08-18 17:11:57.266  7863 16796 W ActivityManager:   Force finishing activity kr.co.lottecinema.lcm/.activity.PopupWebViewActivity

<<system.log>>
08-18 17:11:56.034 16536 16536 W System.err: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW cat=[android.intent.category.BROWSABLE] dat=intent://pay?tcode=6000001&mid=00035683&acode=6110002&callback=lotteapp/ }
...
08-18 17:11:56.038 16536 16536 F chromium: [FATAL:jni_android.cc(236)] Please include Java exception stack in crash report

Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919

Tested the issue using Samsung SJ-710F (Android 7.0.0) and Pixel XL (Android 8.1.0) on Chrome Stable# 62.0.3202.84 & Chrome Canary# 64.0.3273.0 and could not reproduce the Crash.

@cruise1008 -- Could you please upgrade to latest stable and let us know if you are still seeing the crash, if yes please provide us with a screen cast and latest generated Crash ID.
Thanks in Advance.

Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.