android.os.TransactionTooLargeException

[Somebody]

I'm working with AMD hardware, and repeatedly running into the error android.os.TransactionTooLargeException.

I have three units;
E-350
E2-1800
A4-5357M

The E-350 works with the prebuilt iso image, but runs into the error.
The other two units both required this patch in order to function at all;
http://git.android-x86.org/?p=platform/hardware/drm_gralloc.git;a=commit;h=53548f35c7492e1da9f30b5d207694dfc31bbd34
The A4 is a RadeonSI "Aruba". I think the E2 is something like a SUMO, not quite sure.

The E and the E2 both sometimes start up and run extremely well (once they're up). The A4 gets up to starting the launcher, which repeatedly crashes. On the A4, the power menu comes up over the launcher crash, and does function -- I am able to control it with the power menu.

[Somebody]

Update; in vesa mode, vga=791, the error does not occur.

[Somebody]

Bumping the binder transaction buffer from 1 to 10 MB made it... less crashy.

On Wednesday, October 9, 2013 9:06:30 AM UTC-4, Somebody wrote:

[Chih-Wei Huang]

2013/10/9 下午9:55 於 "Somebody" <defines...@gmail.com> 寫道：
>
> Bumping the binder transaction buffer from 1 to 10 MB made it... less crashy.
>

Could you provide a patch? Thanks a lot.

[Rahul Jain]

Hi,

is there any patch for this Increase in binder buffer limit? 

Thanks,

Rahul

[Mauro Rossi]

On Wednesday, October 9, 2013 at 3:55:16 PM UTC+2, Somebody wrote:

Bumping the binder transaction buffer from 1 to 10 MB made it... less crashy.

Ten times seems very big compared to default

 

On Wednesday, October 9, 2013 9:06:30 AM UTC-4, Somebody wrote:

I'm working with AMD hardware, and repeatedly running into the error android.os.TransactionTooLargeException.

The error may also be the result of SIGSEGV errors happened before

Do you have logcat to check?

Mauro