hardened_malloc

Java implementations have run-time heap allocator limits configurable with the -Xms and -Xmx options for minimum and maximum heap size, and -Xss for per-thread stack size: java -jar -Xms1024M -Xmx2048M -Xss1M example.jar RAM and CPU and network IO cgroups are harder limits than a process's attempts to bound its own allocation with the VM. TIL about hardened_malloc. Python doesn't have hardened_malloc, and IDK how configurable hardened_malloc is in terms of self-imposed process resource limits. FWIU hardened_malloc groups and thereby contains allocations by size. https://github.com/GrapheneOS/hardened_malloc There is a reason that EVM and eWASM have costed opcodes and do not have socket libraries (blocking or async). The default sys.setrecursionlimit() is 1000; so, 1000 times the unbounded stack size per frame: https://docs.python.org/3/

Everything you mentioned works on GrapheneOS, I wouldn't use it if it didnt, I am personally kind of on the limit of my inconvenience tolerance regarding such things. And don't worry, google services are treated as normal user level apps (1), and are sandboxed like any other user app, so you get perfect compatibility with better privacy and security than your average phone. Even Android Auto works now, issues only arise when dealing with safety net, googles hardware attestation (2). It mostly only affects bank apps, but in my experience most of them work without issues, however Gpay won't work at all no matter what. Personally the only worry I have with GrapheneOS is its crazy dev, he said he will step down (3), but he still does a lot (4). 1. https://grapheneos.org/usage#sandboxed-google-play 2. https://grapheneos.org/usage#banking-apps