Dejank: don't allocate when scrolling lists
The new display list properties introduces in JB were causing numerous and expensive memory allocations while scrolling lists. During a scroll ListView sometimes attempts to apply an offset to views before they are drawn for the first time. This had the side effect of generating a new IllegalStateException and its entire stack trace. The exception was caught inside the display list and never seen by users. Generating an exception is very expensive both in terms of allocated memory and CPU time spent crawling the stack. List scrolls/flings are a common case of this issue but it also happens during various types of animations. A simple alpha animation, for instance, can cause the problem to occur. Another side effect of this issue is more frequent and longer GC pauses. Change-Id: Ic1b37cc84f7c8f290209cfb990d030e96d6e0dc7
Loading
Please register or sign in to comment