133.0.6943.60 crash #1814
Comments
|
I am rewriting your stacklog here because it is a bit illegible: |
the first strange thing, which android distribution are you using? |
and this second one: why |
and there is also a third one: why |
One UI 7, Android 15. Currently in beta for S24 series, in stable for S25 series. I will test on S25 next week. I can confirm Chrome 133.0.6943.49 behaves as expected.
Thank you. |
|
it is not cromite. |
From github via the internal update mechanism, as usual. An in-place upgrade from 132 to 133, it could not be anything else or the signatures would not match. I submit this screen recording, please let me know anything else that may be useful. Screen_Recording_20250213_015754_One.UI.Home.mp4 |
|
call stack: |
thanks!
so, where did you get as soon as https://github.com/uazo/cromite/actions/runs/13281053139 finishes I'll look at it. |
This will be Vanilla Chromium 132, also from cromite github. Log for cromite 133: Details
vs. log for Vanilla Chromium 132: Details
Many thanks 👍 |
|
you know i don't think that's the bug? From what I can see, you have a rooted device: could you check whether you have any files in ‘/data/tombstones’? If so, could you send them to me? |
My device is not rooted, however I was able to recover the tombstones via adb bugreport. |
|
perfect! just as I thought. at first glance it looks like a UAF. |
|
I checked the crash log, that piece of code should not even enter since the This seems to be what happens: if you can't lose your data, let me know so we can try another way. EDIT: did you by any chance enable the ‘enable-magic-stack-android’ flag? |
If it is possible to try another way first, i would like to do so, at least to extract the latest bookmarks. e.g. by downgrading with ADB.
This flag seems enabled by default in Vanilla Chromium 132.0.6834.163, disabled by default on cromite 133.0.6943.49. If ADB downgrade is successful I can check this. |
yes, I can create an ad-hoc release with some additional logs and check. However, one thing I do not understand: what is that? theoretically in android an application cannot see the logcat of another application, that's why I thought you had a rooted device
yes, like many others, all google experiments, some good, some better to avoid. for that I don't recommend using it, I only need it for testing. |
|
uazo - v133.0.6943.60 in Windows Sandbox (modern hardware) the
With a command like the following to read logs onslaught86 - I suppose you can't downgrade on your A.15, since Google changed/crippled the behavior in A.14 and now unless you installed before with a rollback parameter/attribute, you can't downgrade (-d param/attrib), only if the package is debuggable (should be explicitly set in the manifest). |
|
Hello @uazo |
Preliminary checklist
Can the bug be reproduced with corresponding Chromium version?
No
Are you sure?
Yes
Cromite version
133.0.6943.60
Device architecture
arm64-v8a
Platform version
Android 15
Android Device model
Samsung Galaxy S24 Ultra
Is the device rooted?
No
Changed flags
#android-bottom-toolbar#android-open-pdf-inline#darken-websites-checkbox-in-themes-setting#enable-smart-zoom#enable-quic
There may be more, however I cannot confirm as cromite crashes on launch.
Is this bug happening ONLY in an incognito tab?
No
Is this bug caused by the adblocker?
No
Is this bug a crash?
Logcat filtered by error:
ConnectivityService: RemoteException caught trying to send a callback msg for NetworkRequest [LISTEN id=3555, [ Capabilities: INTERNET& NOT_RESTRICTED&TRUSTED&FORE GROUND&NOT_VCN_MANAGED&N OT_BANDWIDTH_CONSTRAINED Forbidden: LOCAL_NETWORK Uid: 10551 RequestorUid: 10551 RequestorPkg: org.chromium.chrome UnderlyingNetworks: Null
Verbose logcat:
11:39
on
Log-2025-02-12_23-35-23
? 02-12 23:35:25.562 14008 14008
---12 Feb 2025 11:35:23 pm--.
D ConnectivityManager: StackLog: [android.net.ConnectivityManager.sendRequestFo rNetwork(ConnectivityManager.java:4692)] [androi d.net.ConnectivityManager.registerDefaultNetwor kCallbackForUid(ConnectivityManager.java:5381)] [android.net.ConnectivityManager.registerDefaultN etworkCallback(ConnectivityManager.java:5348)] [RQ0.c(chromium-ChromePublic.apk-stable-69430 6004:42)] [lm1.r(chromium-ChromePublic.apk-s
D
table-694306004:7)] [Im1.b(chromium-ChromeP ublic.apk-stable-694306004:7)] [SQ0.(chro mium-ChromePublic.apk-stable-694306004:109)] [org.chromium.net.NetworkChangeNotifier.setAut oDetectConnectivity State(chromium-ChromePublic .apk-stable-694306004:29)] [ng1.run(chromium-Chr omePublic.apk-stable-694306004:200)] [rx.run(chro mium-ChromePublic.apk-stable-694306004:52)]
02-12 23:35:25.562 2530 6404 D ConnectivityService: requestNetwork for uid/pid:10337/14008 activeRequest: null callbackRequest: 3418 [NetworkRequest [ REQUEST id=3419, [ Capabilities:
D
INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VC N_MANAGED&NOT_BANDWIDTH_CONSTRAINED Uid: 10337 RequestorUid: 10337 RequestorPkg: org.cromite.cromite UnderlyingNetworks: Null]] callback flags: 0 order: 2147483647 isUidTracked false declaredMethods: ALL
02-12 23:35:25.562 2530 3456 D ConnectivityService: accepting network in place of null for NetworkRequest [REQUEST id=3419,[ Capabilities:
D
INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VC N_MANAGED&NOT_BANDWIDTH_CONSTRAINED Uid: 10337 RequestorUid: 10337 RequestorPkg: org.cromite.cromite UnderlyingNetworks: Null]]
02-12 23:35:25.562 14008 14008
D ConnectivityManager: StackLog:
[android.net.ConnectivityManager.sendReques tForNetwork[ConnectivityManager.java:4692)] [android.net.ConnectivityManager.sendReque stForNetwork/(ConnectivityManager.java:4859)] [android.net.ConnectivityManager.registerNet workCallback(ConnectivityManager.java:5241)]
D
[RQ0.c(chromium-ChromePublic.apk-stable-6943 06004:84)] [Im1.r(chromium-ChromePublic.apk- stable-694306004:7)] [Im1.b(chromium-Chrome Public.apk-stable-694306004:7)] [SQ0.(chro nium-ChromePublic.apk-stable-694306004:109)] [org.chromium.net.NetworkChangeNotifier.setAut DetectConnectivityState(chromium-ChromePublic apk-stable-694306004;29)] [ng1-.run(chromium-Chr omePublic.apk-stable-694306004:200)] [rx.run(chro mium-ChromePublic.apk-stable-694306004:52)]
D
02-12 23:35:25.563 2530 3456 D
ConnectivityService: Rematched networks [computed 0ms] [applied 1ms] lissued 0]
D
02-12 23:35:25.563 2530 3456 D ConnectivityService: NetworkReassignment:
D
02-12 23:35:25.563 2530 3456 D Connectivity Service: 3419:null->120
D
02-12 23:35:25.564 2530 3456 D
Connectivity Service: Rematched networks [computed Oms| [applied 1ms] issued 0]
D
02-12 23:35:25.564 2530 3456 D ConnectivityService: NetworkReassignment:no changes
02-12 23:35:25.920 2530 3456 D
Connectivity Service: releasing NetworkRequest [ REQUEST id=3419,[ Capabilities
D
INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VC N_MANAGED&NOT_BANDWIDTH_CONSTRAINED Uid: 10337 RequestorUid: 10337 RequestorPkg: org.cromite.cromite UnderlyingNetworks: Nullj] (release request)
02-12 23:35:25.921 2530 3456D
D ConnectivityService: Removing from current network [120 WIFIl), leaving 193 requests,
?
--12 Feb 2025 11:35:28 pm --"
Describe the bug
Hi master uazo,
Humbly requesting your help to diagnose this strange crash on Galaxy S24 Ultra. Upon upgrading from 132.0.6834.163 to 133.0.6943.60, cromite crashes instantly on launch. Please see attached verbose logcat.
This does not occur on 133.0.6943.60 on 2x other handsets, Pixel 7 Pro (Android 15) or ASUS ROG Phone 7 (Android 13). As no others have reported the crash, it may not be widespread.
I would love to test Vanilla Chromium 133.0.6943.60, however this build does not appear to have been uploaded yet. I can confirm the crash does not occur on Vanilla Chromium 132.0.6834.163.
Many thanks for your hard work on this wonderful project.
Steps to reproduce the bug
Upgrade from 132.0.6834.163 to 133.0.6943.60. Launch cromite.
Expected behavior
Cromite should not crash.
Screenshots
No response
The text was updated successfully, but these errors were encountered: