Not sure when this started - but my CHASE bank mobile app will no longer run on any of my profiles.

I have removed - rebooted - re-installed - cleared cache/data, etc...

The initial screen flashed on then goes away.. the app is still running but if I select it - same thing happens.

    lcalamar

    Sounds like it could be crashing because of a memory leak in their app or something. You can see if that's the case by enabling exploit protection compatibility mode.

    Settings > Apps > See all apps > Chase Mobile > Exploit protection compatibility mode

      Just to add to @unwat's useful reply with a confirmation of the above. Chase does have a memory corruption issue currently that makes it crash unless you enable the Exploit Protection Compatibility Mode for that specific app, so it'll stop using hardened_malloc.

      Keep in mind that this is a feature, not a bug. Ideally Chase needs to fix their memory corruption issue, but GrapheneOS strives to provide as much app compatibility mode, so the above toggle was added to ensure that people can use apps the same way they would on Stock OS, even if they have a memory corruption issue.

        unwat WOW... that fixed it - thank you very much!

        Hopefully I'll remember to try that next time...

        ?? is it a good idea to enable EPCM - on all apps or only when they fail?

          lcalamar ?? is it a good idea to enable EPCM - on all apps or only when they fail?

          Only when they fail. You want hardened_malloc to be enabled for your apps, it's a gigantic security boost. That toggle is only there for problematic apps.

          A very short, non-exhaustive list of apps with memory corruption issues that hardened_malloc has caught recently:

          • Waze
          • Instagram
          • Chase
          • Many old games that use Unity

          matchboxbananasynergy Thanks for the explanation.

          In general it seems financial (i.e. mobile bank apps) are pretty poorly developed... Their attempts to be highly secure just creates needless complexity and non-rational issues...

            matchboxbananasynergy unless you enable the Exploit Protection Compatibility Mode for that specific app, so it'll stop using hardened_malloc.

            Keep in mind that this is a feature, not a bug.... the above toggle was added to ensure that people can use apps the same way they would on Stock OS, even if they have a memory corruption issue.

            What are the possible security and privacy risks of enabling Exploit Protection Compatibility Mode that would not come into play otherwise?

              ve3jlg I'm afraid that I'm not qualified to speak on the specifics of this, but this toggle makes this specific app stop using hardened_malloc and instead use the normal memory allocator that AOSP uses.

              By enabling this toggle for a specific app, you're not downgrading yourself below AOSP. You're just using what AOSP uses for that specific app.

              More information on hardened_malloc and what it provides can be found here:

              https://github.com/GrapheneOS/hardened_malloc#introduction