What's the rationale for hard-coding stack sizes at 8k? That's pretty small, even for Java apps that don't allocate things on the stack. Windows will actually grow the stack for you when you exceed the limits, up to the point at which you run out of memory.
This really isn't a Views-heirarchy specific issue is it. Theoretically any app that is close to the 8k limit can be broken by having some additional recursion in a platform library. Growing the stack automatically appears to be the only robust, general solution. BTW I hope one day we have escape analysis/stack allocation in Dalvik. That'd probably go a long way towards taking the pressure off the GC system and making it easier to write smoothly performing games. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
