-
Notifications
You must be signed in to change notification settings - Fork 212
art/runtime/stack.cc:205] Check failed: success Failed to read the this object in void ....handleLoadPackage(de.robv.android.xposed.callbacks.XC_LoadPackage$LoadPackageParam) #72
Comments
This is probably one of the issues mentioned here: #72 |
@rovo89 you mean here rovo89/Xposed#275 |
These crashes should be fixed with v89 which I released last night. |
I'm still seeing this issue with v89. C3 Toolbox is not running after boot and doesn't start when selected in the launcher. Xposed log is full of: 12-19 08:59:38.752 F/art ( 3972): art/runtime/stack.cc:205] Check failed: success Failed to read the this object in void ccc71.at.xposed.at_xposed_enabled.handleLoadPackage(de.robv.android.xposed.callbacks.XC_LoadPackage$LoadPackageParam) See my comments in issue rovo89/Xposed#275 for additional information. |
Sorry to hear that.
I’m running v89 on top of Magisk and have no issues so far.
Are you sure v89 is loaded? Have you tried the ‘fix’ referred in rovio threads:
cmd package compile --reset ccc71.at
Many users have reported it fixes the issue, however it might only be temporary?
It might be permanent if the issue comes from ‘old’ cache still providing old code somehow.
3C.
De : eFrysTon [mailto:[email protected]]
Envoyé : mardi 19 décembre 2017 01:32
À : rovo89/android_art <[email protected]>
Cc : 3c71 <[email protected]>; Author <[email protected]>
Objet : Re: [rovo89/android_art] art/runtime/stack.cc:205] Check failed: success Failed to read the this object in void ....handleLoadPackage(de.robv.android.xposed.callbacks.XC_LoadPackage$LoadPackageParam) (#72)
I'm still seeing this issue with v89.
C3 Toolbox is not running after boot and doesn't start when selected in the launcher.
Xposed log is full of:
12-19 08:59:38.752 F/art ( 3972): art/runtime/stack.cc:205] Check failed: success Failed to read the this object in void ccc71.at.xposed.at_xposed_enabled.handleLoadPackage(de.robv.android.xposed.callbacks.XC_LoadPackage$LoadPackageParam)
12-19 09:00:00.485 F/art ( 4926): art/runtime/stack.cc:205] Check failed: success Failed to read the this object in void ccc71.at.xposed.at_xposed_enabled.handleLoadPackage(de.robv.android.xposed.callbacks.XC_LoadPackage$LoadPackageParam)
12-19 09:01:32.055 F/art ( 5919): art/runtime/stack.cc:205] Check failed: success Failed to read the this object in void ccc71.at.xposed.at_xposed_enabled.handleLoadPackage(de.robv.android.xposed.callbacks.XC_LoadPackage$LoadPackageParam)
12-19 09:04:54.503 F/art ( 9789): art/runtime/stack.cc:205] Check failed: success Failed to read the this object in void ccc71.at.xposed.at_xposed_enabled.handleLoadPackage(de.robv.android.xposed.callbacks.XC_LoadPackage$LoadPackageParam)
....
See my comments in issue #275 for additional information.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#72 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AFfdxmZ-AYPPeKLnTeHifsBg_weySs-Qks5tBwQKgaJpZM4Q4nEa> . <https://github.com/notifications/beacon/AFfdxrrt3A3kio8r2iGD3JbF3pYs8wOVks5tBwQKgaJpZM4Q4nEa.gif>
|
I'm very sure I'm running v89 correctly. It's fine right after I boot to system from recovery after wiping dalvik/art cache and cache, but it starts/keeps failing again after some time. I'm pretty sure it's directly related to the issues caused by BackgroundDexOptService described in rovo89/Xposed#275 |
Then I'll have to look at these issues again next year. For now, my focus is on Oreo, especially as the latest fixes seem to work for most people. I'd just like to mention again that the background dexing and resetting the compiled code is just about the symptoms. Please don't call this a fix. |
I built an Xposed module since a few years, and users are now reporting a weird issue in which the app itself no longer starts when its integrated module is enabled.
When module is enabled, the Xposed logs shows many lines like this:
art/runtime/stack.cc:205] Check failed: success Failed to read the this object in void ccc71.at.xposed.at_xposed_enabled.handleLoadPackage(de.robv.android.xposed.callbacks.XC_LoadPackage$LoadPackageParam)
Not sure what it means or if it relates to the app no longer starting, but it's odd enough as the method in question is quite simple:
Can anybody help me understand how an Xposed module being enabled would prevent the hosting app from starting? There's nothing in logcat, no ANR nor any tombstones when this happens. Just those lines in the log attached.
xposed_error_20171206_062700.log
The text was updated successfully, but these errors were encountered: