ORBot install fails when installing/uncompressing tor binary

This is a bug report for 0.2.2.22-orbot-alpha-1.0.5.20110417a-dev, running on CM6.1.0-RC2 (Desire HD).

It seems like ORBot fails to unzip the tor binary to the data directory, as it is too large to fit in the dedicated memory for that operation (...or so Google tells me).

Additionally (not sure if that should be a second bug), ORBot still declares the operation successful, even though it is caught by the exception handler. This, of course, leads to ORBot trying (and failing) to start afterwards, constantly receiving -1 as the pid (if you want to detect unrecoverable situations, that might be one approach - keep in mind that I haven't read the corresponding code, maybe ORBot is already doing that).

Logcat (useless messages redacted):

I/ActivityManager( 1487): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.torproject.android/.Orbot } I/ActivityManager( 1487): Start proc org.torproject.android for activity org.torproject.android/.Orbot: pid=23812 uid=10105 gids={3003} I/ORBOT (23812): service started: org.torproject.android.service.TOR_SERVICE D/ORBOT (23812): Tor binary exists=false D/ORBOT (23812): Privoxy binary exists=false D/asset (23812): Data exceeds UNCOMPRESS_DATA_MAX (3188430 vs 3145728) D/ORBOT (23812): Error writing output file '/data/data/org.torproject.android/app_bin/tor': java.io.IOException D/ORBOT (23812): SUCCESS: installed tor, privoxy binaries from raw

Should I try running it on CM7 instead?

Trac:
Username: __sporkbomb