UIDragScrollView.OnDisable() perf question

[Zyxil]

Is this OnDisable() even necessary to have?  It allocs a bunch of junk for the GC to clean up.  With a very large number of elements, I'm seeing 80+ % in 2 second frames when destroying and recreating lists. 

[Zyxil]

Here is a Profiler view.  Don't worry about the 40s time, this is a Deep Profile.

This was a 400 element list in a scrollview and it alloc'd 453mb, over 255mb worth in CalcRelativeWidgetBounds().   

[ArenMook]

Curious... How about we add a "if (mPressed == pressed) return;" check to the very top of UIScrollView.Press?

[Zyxil]

That relieves the massive alloc from DestroyChildren() down to 0b. It's still a time sink (about 40% of total fame time), which is reasonable as (in this case) I'm destroying 553 compound widgets.

Of course, I'm not going to allow this many items in the list during normal operations. I was testing to find the sweet spot when I noticed the memory consumption.

Will you be making this change to the codebase?  If so, I'll just leave this tweak in and forget about it and the next upgrade will magically cause no issues.   

[ArenMook]

Yup, I've made the change locally so it will be like that in the next update. Thanks for confirming.