Rafael Ristovski

Hmm, is `0x200` the address for one of the `SP_EL1/2/3` exception level handlers? Also, 16777216 is `0x1000000`, which somehow /feels/ relevant. Sadly my aarch64 knowledge is lacking Have you tried...

You will have to reverse engineer your phones `fastrpc_shell_0` and find the check. Example for MSM8953 - Motorola Potter (relevant line highlighted, taken from [Cutter](https://cutter.re/)):  The patch in this...

~Seems like even `apktool --no-res` (no resources) fails as well - the apk gets built but crashes with "resource not found" in logcat once installed.~ Edit: seems like this has...

Are there any updates to this? I noticed `AsyncEventBus` has been removed (but `AsyncEventBusPerformance.cpp` added in the same commit??), but I can not see an alternative mechanism for consuming events...

Any news on this? Having an AppImage would be wonderful.

@AlexFolland Please try the following: `gdb --args ./chamfer -C --experimental --no-host-memory-import --no-scissoring`, then inside gdb, enter the command `r`, once it crashes, use `bt` to grab the backtrace and paste...

Try this: `gdb -ex run -ex bt -ex quit --args ./chamfer -C --experimental --no-host-memory-import --no-scissoring`

Very weird. I suppose @jaelpark might be able to provide any ideas. I would try commenting out https://github.com/jaelpark/chamferwm/blob/master/src/backend.cpp#L744-L745 just to see what would happen (maybe along with the allocation code...

Oh oops, that was by mistake. You should be able to find the same code in that branch as well.

Any updates/workarounds on this?