Hi fadden,
Here is the stack trace:
05-21 08:38:08.050: ERROR/AndroidRuntime(952): Uncaught handler:
thread main exiting due to uncaught exception
05-21 08:38:08.098: ERROR/AndroidRuntime(952):
java.lang.StackOverflowError
05-21 08:38:08.098: ERROR/AndroidRuntime(952): at
But I'm confident I don't deal with so much levels.
I count about 30 draw() calls on either ViewGroup or FrameLayout in
the stack.
You are dealing with quite a number of levels... probably too many of
them.
On May 21, 4:44 am, Vince vincent.gann...@gmail.com wrote:
Hi fadden,
Here is the
Indeed, you're right. Which does not explain why a single character
can cause the all app to crash :-(
Any guess?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send
On May 21, 9:30 am, Vince vincent.gann...@gmail.com wrote:
Indeed, you're right. Which does not explain why a single character
can cause the all app to crash :-(
Any guess?
It could be that the additional StringBuilder operations for the
string concatenation affected something. Could be
On May 20, 2:25 pm, Vince vincent.gann...@gmail.com wrote:
It's driving me mad. I read on a post that such StackOverflow
exception could be caused by a hierarchy 15 levels deep. But I'm
confident I don't deal with so much levels.
What does the exception stack trace look like?
5 matches
Mail list logo
