Skip to content
This repository has been archived by the owner on Jun 1, 2023. It is now read-only.

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

Open
3c71 opened this issue Dec 6, 2017 · 7 comments

Comments

@3c71
Copy link

3c71 commented Dec 6, 2017

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:

@Override
public void handleLoadPackage(LoadPackageParam lpparam) throws Throwable
{
	String self = at_xposed_helpers.getPackageName();

	if (lpparam.packageName.equals(self))
	{
		findAndHookMethod("ccc71.at.xposed.at_xposed_helpers", lpparam.classLoader, "isXposedEnabled", new XC_MethodHook()
		{
			@Override
			protected void beforeHookedMethod(MethodHookParam param) throws Throwable
			{
				param.setResult(at_xposed_helpers.VERSION);
			}
		});
	}
}

static String getPackageName()
{
    return BuildConfig.XPOSED_PACKAGE;
}

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

@rovo89
Copy link
Owner

rovo89 commented Dec 7, 2017

This is probably one of the issues mentioned here: #72
Please see my latest reply in that issue.

@wanam
Copy link

wanam commented Dec 7, 2017

@rovo89 you mean here rovo89/Xposed#275

@rovo89
Copy link
Owner

rovo89 commented Dec 18, 2017

These crashes should be fixed with v89 which I released last night.

@rovo89 rovo89 closed this as completed Dec 18, 2017
@ElminsterAU
Copy link

ElminsterAU commented Dec 19, 2017

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 rovo89/Xposed#275 for additional information.

@3c71
Copy link
Author

3c71 commented Dec 24, 2017 via email

@ElminsterAU
Copy link

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

@rovo89 rovo89 reopened this Dec 24, 2017
@rovo89
Copy link
Owner

rovo89 commented Dec 24, 2017

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants