Start Building Professional
Web Apps Today

firefox speed

hi

i am sure you have heard of the problems in firefox 3 in relation to large cpu usage over time, especially when using javascript heavy applications.

we use your components (layouts,grids,toolbars,menus etc...) in firefox 3 and heavily use ajax.

we have noticed in firefox 3 it gets slower and slower the more our users use our software. they have to close their browser and restart every 20 mins

we know this is a firefox issue but have you guys ever seen this and do you recommend us to do anything to speed up the application

thanks

>>in firefox 3 and heavily use ajax
Are you using stable 3.0 or experimental 3.1 branch of FF? ( 3.1 branch uses different js engine, which still not finalized and may produce unwanted effects ) 

>>and do you recommend us to do anything to speed up the application
Normal AJAX loading must not cause problems for FF ( it has correct garbage collection logic, and removes unused XML objects from the memory ) 

The performance problem may be related to the architecture of app. If you are constantly creating new object without destroying old ones - similar effect can occurs ( most object has auto-destruction code attached to unload event ) 
Switching from new object creation to reusing of existing ones, can improve situation. 

( if you app loads a lot of  html content with images in dhtmlxwindows|dhtmlxaccordion - another known problem can occur , related to memory leaking, please contact us directly at support@dhtmlx.com if you need a hot-fix for it. )

>>in firefox 3 and heavily use ajax
>>Are you using stable 3.0 or experimental 3.1 branch of FF? ( 3.1 branch uses different js engine, which still not finalized and may produce unwanted effects ) 
we are using firefox 3.0 which is a problem for many which we found out by typing 'firefox 3.0 slow' into google

>> The performance problem may be related to the architecture of app. If you are constantly creating new object without destroying old ones - similar effect can occurs ( most object has auto-destruction code attached to unload event ). Switching from new object creation to reusing of existing ones, can improve situation.

thanks, we will look into this

>> ( if you app loads a lot of  html content with images in dhtmlxwindows|dhtmlxaccordion - another known problem can occur , related to memory leaking, please contact us directly at support@dhtmlx.com if you need a hot-fix for it. )

yes we use alot of windows, layout, and accordion and would like any fix you have

thanks