Closed Bug 819117 Opened 13 years ago Closed 12 years ago

Firefox freezing completely consuming one core at Sony's page

Categories

(Core :: JavaScript Engine, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mz+bugzilla, Unassigned)

References

()

Details

(Keywords: hang, perf)

Not sure, which category is right, so submitting to General. Steps to reproduce: 1) Visit http://esupport.sony.com/perl/select-system.pl?DIRECTOR=DRIVER&SR=nav:support:electronics:drivers_software:esup 2) In Select a product category: click VAIO® Laptop Computers Expected results: Selected category expanded Actual results: Browser freezed, completely consuming one cpu core Additional Info: Quick stack capture on process kill: eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000288 edi=00000000 eip=77a9f8b1 esp=055dfa90 ebp=055dfafc iopl=0 nv up ei pl zr na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246 ntdll!NtWaitForSingleObject+0x15: 77a9f8b1 83c404 add esp,4 0:015> |* ~* kp . 15 Id: 2014.1ca4 Suspend: -1 Teb: fff8b000 Unfrozen ChildEBP RetAddr 055dfa90 76ea149d ntdll!NtWaitForSingleObject+0x15 055dfafc 770c1194 KERNELBASE!WaitForSingleObjectEx+0x98 055dfb14 770c1148 kernel32!WaitForSingleObjectExImplementation+0x75 *** WARNING: Unable to verify checksum for C:\Storage\FF\Firefox\nspr4.dll 055dfb28 6e8922de kernel32!WaitForSingleObject+0x12 *** WARNING: Unable to verify checksum for C:\Storage\FF\Firefox\mozjs.dll 055dfb50 5f62b1ad nspr4!PR_WaitCondVar(struct PRCondVar * cvar = 0x04026820, unsigned int timeout = 0xffffffff)+0x10e [e:\builds\moz2_slave\m-cen-w32-ntly\build\nsprpub\pr\src\threads\combined\prucv.c @ 515] 055dfb5c 5f62b1ec mozjs!js::AutoLockMonitor::wait(void)+0xd [e:\builds\moz2_slave\m-cen-w32-ntly\build\js\src\vm\monitor.h @ 73] 055dfb78 5f62b21c mozjs!js::ThreadPoolWorker::run(void)+0x3c [e:\builds\moz2_slave\m-cen-w32-ntly\build\js\src\vm\threadpool.cpp @ 147] 055dfb84 6e892b0f mozjs!js::ThreadPoolWorker::ThreadMain(void * arg = 0x0400c840)+0xc [e:\builds\moz2_slave\m-cen-w32-ntly\build\js\src\vm\threadpool.cpp @ 115] 055dfba8 6e893d6d nspr4!_PR_NativeRunThread(void * arg = 0x00e10e60)+0x11f [e:\builds\moz2_slave\m-cen-w32-ntly\build\nsprpub\pr\src\threads\combined\pruthr.c @ 417] 055dfbb0 66e1c6de nspr4!pr_root(void * arg = 0x66e1c788)+0xd [e:\builds\moz2_slave\m-cen-w32-ntly\build\nsprpub\pr\src\md\windows\w95thred.c @ 90] 055dfbe8 66e1c788 MSVCR100!_callthreadstartex(void)+0x1b [f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c @ 314] 055dfbf4 770c33aa MSVCR100!_threadstartex(void * ptd = 0x003b99c8)+0x64 [f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c @ 292] 055dfc00 77ab9ef2 kernel32!BaseThreadInitThunk+0xe 055dfc40 77ab9ec5 ntdll!__RtlUserThreadStart+0x70 055dfc58 00000000 ntdll!_RtlUserThreadStart+0x1b
Most of the time seems to be spent inside "JSC::Yarr::interpret". When I click Debug in the Slow Script dialog I get: ------------------------------------------------------------------------ Hit JavaScript "debugger" keyword. JS call stack... 0 f() ["http://esupport.sony.com/foresee/foresee-trigger.js":198] this = [object Window] 1 anonymous() ["http://esupport.sony.com/foresee/foresee-trigger.js":200] this = function (a,b){var d=a.document;return m.sb.cc(function(a){var b="";try{if(c.S&&(a.compatMode!="CSS1Compat"||a.documentMode==5))return b;var d= a.doctype;if(d){b="<!DOCTYPE HTML";d.publicId&&(b=b+' PUBLIC "'+d.publicId+'"');d.systemId&&(b=b+' "'+d.systemId+'"');b=b+">"}else{var l=a.childNodes,a=0;if(l[a].text){for(;l[a].text&&(l[a].text.indexOf("<\!--")==0||l[a].text.indexOf("<?xml")==0);)a++;cdt=l[a].text.toLowerCase();if(cdt.indexOf("<!doctype")==0)b=l[a].text}}}catch(g){}return b}(d)+j.k("html",d).outerHTML(),u,b)} 2 anonymous() ["http://esupport.sony.com/foresee/foresee-trigger.js":212] this = [object Window] ------------------------------------------------------------------------
Assignee: nobody → general
Component: General → JavaScript Engine
Sony fixed their page so no longer reproducible...
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.