PDA

View Full Version : [CLOSED]Ext 4 examples "pause" when running with FB open



mankz
6 Mar 2011, 11:29 PM
If I have Firebug open as I load an Ext 4-example, it pauses and shows me this line (no exception thrown):



evaluatedFn = function(values, parent, xindex, xcount){return ['<div class="',(values['baseCls'] === undefined ? '' : values['baseCls']),'-body',this.applySubTemplate(0, values, parent, xindex, xcount),'"',this.applySubTemplate(1, values, parent, xindex, xcount),'></div>'].join('');};


I can then press play button and example runs as expected, any idea why this happens?

stack:



evaluatedFn(Ext=undefined)37 (rad -301)
evaluatedFn(values=Object { baseCls="x-panel-header", componentCls="x-panel-header", frame=false}, parent=Object {}, xindex=1, xcount=1)37 (rad -301)
compiled(values=Object { baseCls="x-panel-header", componentCls="x-panel-header", frame=false}, parent=Object {}, xindex=1, xcount=1)ext-all-debug.js (rad 764)
applySubTemplate(id=1, values=Object { baseCls="x-panel-header", componentCls="x-panel-header", frame=false}, parent=Object {}, xindex=1, xcount=1)ext-all-debug.js (rad 685)
evaluatedFn(values=Object { baseCls="x-panel-header", componentCls="x-panel-header", frame=false}, parent=Object {}, xindex=1, xcount=1)37 (rad 1)
compiled(values=Object { baseCls="x-panel-header", componentCls="x-panel-header", frame=false}, parent=Object {}, xindex=1, xcount=1)ext-all-debug.js (rad 793)
applyTemplate(values=Object { baseCls="x-panel-header", componentCls="x-panel-header", frame=false})ext-all-debug.js (rad 805)
doInsert(where="beforeEnd", el=div#header-1023.x-panel-header, values=Object { baseCls="x-panel-header", componentCls="x-panel-header", frame=false}, returnEl=undefined)ext-all-debug.js (rad 293)
append(el=Object { dom=, id="header-1023", more...}, values=Object { baseCls="x-panel-header", componentCls="x-panel-header", frame=false}, returnElement=undefined)ext-all-debug.js (rad 288)
onRender(container=Object { dom=, id="gridpanel-1016", more...}, position=div#ext-gen1013.x-panel-body)ext-all-debug.js (rad 35372)
render(container=Object { dom=, id="gridpanel-1016", more...}, position=0)ext-all-debug.js (rad 35275)
render(ct=Object { dom=, id="gridpanel-1016", more...}, position=0, overwrite=undefined)ext-all-debug.js (rad 42687)
renderItem(item=Object { initialConfig={...}, title="Restaurants", more...}, target=Object { dom=, id="gridpanel-1016", more...}, position=0)ext-all-debug.js (rad 4737)
renderItems(items=[Object { initialConfig={...}, title="Restaurants", more...}], target=Object { dom=, id="gridpanel-1016", more...})ext-all-debug.js (rad 4708)
beforeLayout()ext-all-debug.js (rad 4691)
callParent(args=[600, 400, true, undefined])ext-core-debug.js (rad 2396)
beforeLayout(width=600, height=400, isSetSize=true, layoutOwner=undefined)ext-all-debug.js (rad 26896)
layout()ext-all-debug.js (rad 4682)
doComponentLayout(width=600, height=400, isSetSize=true, ownerCt=undefined)ext-all-debug.js (rad 36388)
setSize(width=600, height=400)ext-all-debug.js (rad 36324)
afterRender()ext-all-debug.js (rad 35389)
afterRender()ext-all-debug.js (rad 42707)
callParent(args=undefined)ext-core-debug.js (rad 2396)
afterRender()ext-all-debug.js (rad 52311)
render(container=Object { dom=, id="ext-gen1008", more...}, position=undefined)ext-all-debug.js (rad 35288)
render(ct=Object { dom=, id="ext-gen1008", more...}, position=undefined, overwrite=undefined)ext-all-debug.js (rad 42687)
constructor(config=Object { renderTo={...}, store={...}, more...})ext-all-debug.js (rad 35117)
constructor(config=Object { renderTo={...}, store={...}, more...})ext-all-debug.js (rad 42665)
newClass()ext-core-debug.js (rad 2929)
(?)()groupgrid.js (rad 234)
call()ext-core-debug.js (rad 12829)

vladsch
7 Mar 2011, 12:59 AM
Hi,

The same behaviour under IE8 with debug mode (for example, if run the page under Visual Studio with debugging). VS shows huge of 'eval' executions. I already posted about it (just I did not notice first that debugging mode is the issue)
http://www.sencha.com/forum/showthread.php?125138-CLOSED-IE8-Slow-first-calling-of-Ext.Msg.alert

evant
7 Mar 2011, 1:05 AM
It's breaking on the error, fairly sure that gets wrapped in a try/catch. The same thing will happen on Chrome.

mankz
7 Mar 2011, 1:06 AM
@evant, any idea about the cause?

evant
7 Mar 2011, 3:33 AM
Run this:



try {
return foo;
} catch (e) {
console.log('blah');
}

mankz
7 Mar 2011, 5:08 AM
Not sure what you mean:



>>> try { return "foo"; } catch (e) { console.log('blah'); }
SyntaxError: return not in function


All the Ext 4 examples show this behaviour when running them with FB open, surely not what you want..?

steffenk
7 Mar 2011, 7:29 AM
Hi manks,

i can't confirm that here. I run them on FF4b and FB1.7X0.b1. They work fine with opened console.
Maybe it's illumination that makes problems?

mankz
7 Mar 2011, 7:31 AM
Don't have any FB plugins activated, running Firefox 3.6.15

steffenk
7 Mar 2011, 7:38 AM
try switch to FF4b - it's worth to do!