On Oct 28, 11:31 pm, Samuh <[email protected]> wrote: > However, when the user was trying to open an image from the SD card > the app ran into strange errors. > > Stack dump : > > 10-29 08:51:35.536: ERROR/IMemory(18142): binder=0x191868 transaction > failed fd=-2147483647, size=0, err=-2147483646 (Unknown error: > 2147483646) > 10-29 08:51:35.536: ERROR/IMemory(18142): cannot dup fd=-2147483647, > size=0, err=-2147483646 (Bad file number) > 10-29 08:51:35.536: ERROR/IMemory(18142): cannot map BpMemoryHeap > (binder=0x191868), size=0, fd=-1 (Bad file number) > 10-29 08:51:35.555: ERROR/Surface(18142): Couldn't map Surface's heap > (binder=0x191868, heap=0x1918c0) [...] > 10-29 08:51:35.675: ERROR/AndroidRuntime(18142): > java.lang.IllegalArgumentException > 10-29 08:51:35.675: ERROR/AndroidRuntime(18142): at > android.view.Surface.lockCanvasNative(Native Method)
Looks like some of the core framework stuff went a little nutty. -2147483647 is 0x80000001, so seeing that in a file descriptor is a bit weird. Something low-level failed and the problem bubbled up; maybe a magic error result got passed back in an fd result and didn't get trapped. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
