java.lang.StackOverFlow error. Suspected too many views?

Question

When you get an error like the one below (Android 1.5), is it because there are too many nested ViewGroups, or because the total number of Views is too great? Are there any tricks to get around it while still keeping the same look to your app?

java.lang.StackOverflowError
   at android.text.Styled.measureText(Styled.java:371)
   at android.text.Layout.measureText(Layout.java:1600)
   at android.text.Layout.getLineMax(Layout.java:654)
   at android.text.Layout.draw(Layout.java:310)
   at android.text.BoringLayout.draw(BoringLayout.java:356)
   at android.widget.TextView.onDraw(TextView.java:3921)
   at android.view.View.draw(View.java:5838)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1486)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1484)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.widget.AbsListView.dispatchDraw(AbsListView.java:1319)
   at android.widget.ListView.dispatchDraw(ListView.java:2820)
   at android.view.View.draw(View.java:5944)
   at android.widget.AbsListView.draw(AbsListView.java:2121)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1486)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1484)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.View.draw(View.java:5841)
   at android.widget.FrameLayout.draw(FrameLayout.java:352)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1486)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1484)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.View.draw(View.java:5841)
   at android.widget.FrameLayout.draw(FrameLayout.java:352)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1486)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.View.draw(View.java:5841)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1486)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.View.draw(View.java:5841)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1486)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.View.draw(View.java:5841)
   at android.widget.FrameLayout.draw(FrameLayout.java:352)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1486)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1484)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.ViewGroup.drawChild(ViewGroup.java:1484)
   at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1228)
   at android.view.View.draw(View.java:5841)
   at android.widget.FrameLayout.draw(FrameLayout.java:352)
   at com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1847)
   at android.view.ViewRoot.draw(ViewRoot.java:1217)
   at android.view.ViewRoot.performTraversals(ViewRoot.java:1030)
   at android.view.ViewRoot.handleMessage(ViewRoot.java:1482)
   at android.os.Handler.dispatchMessage(Handler.java:99)
   at android.os.Looper.loop(Looper.java:123)
   at android.app.ActivityThread.main(ActivityThread.java:3948)
   at java.lang.reflect.Method.invokeNative(Native Method)
   at java.lang.reflect.Method.invoke(Method.java:521)
   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
   at dalvik.system.NativeStart.main(Native Method)

hey what the solution to this problem?? @synic

Venkat
– Venkat

2013-06-07 11:09:05 +00:00
Commented Jun 7, 2013 at 11:09 — Venkat
– Venkat, Commented Jun 7, 2013 at 11:09
what is the solution of this problem....

NagarjunaReddy
– NagarjunaReddy

2013-08-20 10:45:29 +00:00
Commented Aug 20, 2013 at 10:45 — NagarjunaReddy
– NagarjunaReddy, Commented Aug 20, 2013 at 10:45

Romain Guy · Accepted Answer · 2010-05-04 16:38:40Z

33

You have (way) too many nested layouts. You can check out the official Android blog at d.android.com to get tips and tricks on how to optimize layouts.

answered May 4, 2010 at 16:38

Romain Guy

98.6k18 gold badges221 silver badges200 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Alex Volovoy Over a year ago

flatten your view hierarchy by replacing your layouts with relative. Series of articles that Romain suggested here : android-developers.blogspot.com/search/label/Optimization

neteinstein Over a year ago

The question is: How much is too much? Is it documented?

neteinstein Over a year ago

Update: info about a possible reference value: stackoverflow.com/questions/9946368/…

Marcelo Noguti Over a year ago

Indeed it was the problem I have been facing til now. Just had to rearrange some nested views. Thanks!

Ishtiaq · Accepted Answer · 2015-09-07 06:49:27Z

6

in my case I resolved by in

onCreateView

        rootView = inflater.inflate(R.layout.fragment_interest_list, container);
        return rootView;

by adding attachToRoot parameter

         rootView = inflater.inflate(R.layout.fragment_interest_list,container,false);
         return rootView;

answered Sep 7, 2015 at 6:49

Ishtiaq

1,2069 silver badges18 bronze badges

2 Comments

vanomart Over a year ago

In my case this didn't work, I had to change it to inflater.inflate(R.layout.some_layout, null)

Abhinav Puri Over a year ago

In my case, i previously had : rootView = inflater.inflate(R.layout.fragment_layout, container, true); I set it to : rootView = inflater.inflate(R.layout.fragment_layout, container, false), and voila ! it worked.

JPMagalhaes · Accepted Answer · 2012-12-05 15:01:48Z

5

In my case it was caused by nested layouts (complex list itens) in a list inside a fragment view pager inside another fragment, using v4 support and HoloEverywhere v1.4 libraries.

I had to remove nested fragments and build it in a different way.

answered Dec 5, 2012 at 15:01

JPMagalhaes

3,6211 gold badge27 silver badges26 bronze badges

Comments

akjoshi · Accepted Answer · 2012-11-17 10:59:53Z

2

In my case,

Customized list view has Relative Layout, then it released Stackoverflowerror.

If your listview has relative layout, then erase it :D

edited Nov 17, 2012 at 10:59

akjoshi

15.8k13 gold badges108 silver badges122 bronze badges

answered Jul 11, 2011 at 13:41

larsien

13910 bronze badges

1 Comment

dell116 Over a year ago

In my case this did it for me. Having a ListView, inside a fragment view pager, inside a fragment view pager, with a RelativeLayout was causing crashes on API's < 14. Removing the RelativeLayout re-working the listview's layout did the trick (and performance is also much better).

Community · Accepted Answer · 2017-05-23 12:34:10Z

0

In my case that was ListView inside a ScrollView and when I try to Scroll it to the bottom. It produces stackoverflow error.

So, avoid to have ListView inside ScrollView.

Or we can use different approach to implement ListView.

Android list view inside a scroll view

edited May 23, 2017 at 12:34

CommunityBot

11 silver badge

answered Jan 1, 2014 at 17:14

Vinit Siriah

3273 silver badges12 bronze badges

Comments

Dr TJ · Accepted Answer · 2016-08-09 15:01:18Z

0

In my case and in XamarinForms, I solved this error by adding CachingStrategy="RecycleElement" to my ListView and also removing extra layouts.
Android users should use RecyclerView or other view recycling methods.

answered Aug 9, 2016 at 15:01

Dr TJ

3,3942 gold badges38 silver badges55 bronze badges

Comments

Pablo López Martínez · Accepted Answer · 2016-11-03 09:35:38Z

0

For Xamarin Forms in our case using ListViews didn't resolve the issue, the exception kept raising on a carousel we have, and we can't call the draw method from another thread because some graphics painted with NControl we need doesn't allow us to do that (OpenGL related I guess). So in the end just catching the exception in our carousel custom renderer and calling Invalidate() on it resolved the problem.

answered Nov 3, 2016 at 9:35

Pablo López Martínez

2412 silver badges3 bronze badges

Collectives™ on Stack Overflow

java.lang.StackOverFlow error. Suspected too many views?

7 Answers 7

4 Comments

2 Comments

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

4 Comments

2 Comments

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related