I am seeing some behavior that is hard to pin down. I get a StackOverFlow exception generated whenever a button in one fragment is clicked rapidly in succession and causes a second fragment on the screen to reload repeatedly. The exception only happens when the use "hammers" on the button for a minute or so. The views aren't that deep, but the amount of data in each fragment is variable.
Has anyone seen this who can recommend a work-around or a solution that prevents this from happening? Here's a more complete description: I have a screen with two fragments on it. Each fragment is bound to its own FrameLayout control. The first fragment displays a button as part of its view. The second fragment displays a list view fragment. When the user presses the button in the first FrameLayout (fragment A), it causes the list view fragment in the second FrameLayout (fragment B) to refresh. Fragment B is a fragment that is reused in the activity - once it's created it's not destroyed until on My unit tester discovered that when you press the button (and consequently cause the list view fragment to reload) very quickly for a minute or so, the application generates a StackOverFlow error. The views aren't that deep either. The first fragment has perhaps 2-4 layers, and the second fragment has perhaps 3-5 layers. The only variable is that the second fragments list view is an arbitrary size. Thanks! -- 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
