Re: Seek help on Crashpad handler behavior in chrome_public_bundle (AAB)

[Andrew Grieve]

+chromium-dev (Use this to email chromium team).

I don't have any guesses based on your description, but I know chrome uses bundles and our crash reporting works.

On Wed, Dec 24, 2025 at 5:13 AM Yu Jiang <yuj...@microsoft.com> wrote:

Hello Chromium  team,

I’m an Android engineer from Microsoft Edge team. I’d like to ask for your advice regarding Crashpad behavior differences we’re observing between APK and App Bundle builds.

Background

In our APK-based builds, the native Crashpad handler (libchrome_crashpad_handler.so) works as expected:

• The handler process can be launched successfully at crash time

• Minidump files are generated correctly

• Native crashes are reported as expected

However, when we switch to App Bundle (AAB) builds generated from the chrome_public_bundle target, we are seeing a different behavior:

• libchrome_crashpad_handler.so fails to start at crash time

• As a result, no minidump is generated

• Native crash reporting is effectively broken for AAB installs

Observations

• The issue only reproduces with AAB-based installs

• The same code and Crashpad configuration work correctly in APK builds

• This appears to be related to how the Crashpad handler binary is packaged, extracted, or launched under App Bundle / split APK scenarios

I observed the same behavior when building both APKs and App Bundles using the latest Chromium codebase. Has Chromium addressed similar issues related to chrome_public_bundle target app bundles? Any guidance, documentation, or pointers to relevant issues would be greatly appreciated. We’d be happy to provide more details if needed.

Thanks,

Yu

获取 Outlook for Mac