Render time of an overnested panel Ext 3 / Ext 4

I've got a similar issue. I posted my overnested code example at the Migration thread first.

I've got an overnested panel with multiple checkboxes. I tried to rebuild a similar example. Created some random Panels including some checkboxes.

With Ext 3.3.0 (ext-all-debug.js and ext-base-debug.js) it will be rendered within 300 up to 400 ms.
Ext 4.0.0 needs more than 40000 ms to render the same configuration in Firefox 4.0.1.

It seems to me that the layout function of Ext.layout.Layout needs a lot of calculation time. Especially Firefox asks at the Line of "me.onLayout.apply(me, arguments);" to stop the script.
[edit: FF4 wants to stop also at the getWidth() method of the Ext.core.Element line 8485 in ext-all-debug.js].

Most of the componentes are using the standard layout.
With using more hbox layouts Ext 4 will render a little bit faster.

It's not an enjoyable mode of development to have to come back to the site twice a day hoping for the next patch release to fix the things that are crippling our upcoming release (slow grid performance, theme problems, bugs).

validation on change with formfields also causes performance loss. If you have validation on your fields and you load it with data maybe at the moment of a tab change, it fires a doLayout or resize for each field on the formpanel. It was possible to block by validateOnChange = false.

If you look at the first example in this thread you see at every formfield an allowBlanc property set to false. In that case it means if you have four fields doLayout on the parentpanel is called four times. With firebug you even get some blocking script messages.

If you look at the first example in this thread you see at every formfield an allowBlanc property set to false. In that case it means if you have four fields doLayout on the parentpanel is called four times. With firebug you even get some blocking script messages.

ok, I modified the allowBlank property (but did you test it yourself?)... and guess what? it is as much slow as before... the problem is not about "allowBlank" property.

I agree rich, this really is a show-stopper and wont move any licences. Customer love the UI but at the moment the application is simply not useable.

tvanzoelen, although i see the your point,simply activate/rendering the form without any action (load etc) takes way too long when nested and with many fieldsets with their own layouts just like tprodigy1 pointed out.