Closed Bug 803702 Opened 13 years ago Closed 13 years ago

burgerking webpage (german) becomes unresponsive after short time

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Version:
SeaMonkey 2.13 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: lahmbi56789, Unassigned)

References

(
URL
)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121011 Firefox/16.0 SeaMonkey/2.13.1 Build ID: 20121011080919 Steps to reproduce: visit http://www.burgerking.de/geschmack-frische wait for the page to load, seems it has a lot of js and videos on it Actual results: after a few seconds Seamonkey becomes slower and slower, finally almost completely unresponsive Expected results: Seamonkey should stay responsive. I tried with Opera, it loads the page without problems, though relatively slow. I turned off hardware acc, soft scrolling etc, still the same. I'm on intel graphics (HD4000, i7-3770S), using the latest intel driver for my board (from ASUS page), Windows 7 64bit.
wfm with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0 SeaMonkey/2.16a1
Hm… That page includes both animated images and embedded plugins (Flash, I expect; but I might be wrong); it also include two different <iframe> subpages For me, on Linux-64 on an Intel "Pentium 4 HT" CPU and with GPU acceleration disabled, the page loads, not really fast though that might be intentional: it seems that each iframe animates when it comes into focus in the visible part of the viewport. But I cannot reproduce the "slower and slower" part: in fact, for me, the first time displays markedly slower than every repetition of the same (perhaps due to image caching). Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/19.0 Firefox/19.0 SeaMonkey/2.16a1 ID:20121019003003 c-c:bd22a204044b m-c:0ff60bfb3442
Possible memory leak? Please go to about:memory to see how much memory this webpage uses.
Hi all, I tried the about:memory with said page, but Seamonkey get's quite fast unresponsive for me, so no joy there, Windows Task Manager shows me something like 200MB (2 tabs open). The memory consumption seems to grow a few 10 kb every few seconds, but nothing dramtically. I should have told you in the bug report, that I deliberately don't have installed any kind of Flash. Maybe that's a quite rare setup, Seamonkey without Flash, but I try to rely on HTML5 videos (youtube still offers some videos only via flash player, quite annoying). I do have Adblock plus installed, though that shouldn't be a problem.
So try this: Help->Restart with Addons Disabled. Do you still see the slowdown?
Hi, I tried with Addons disabled, still the same. Just downloaded and installed Adobe Flash Player, and even with that I'm seeing the slowdown (it's not so much a slowdown, after a few seconds Seamonkey gets almost completely unresponsive). I also tried Firefox 16.0.1 (and Flash installed), same issue there.
Is during irresponsible period your CPU completely used or idle? If first, can you download this tool - http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx, run it, open SeaMonkey (or Firefox) process properties, navigate to Threads tab and look what tread consuming CPU and what it's stack
In Windows Task Manager the CPU is constantly at 13%, which probably means that one thread on one core is at about 100% (afaiu the i7-3770 has 4 cores with two threads each, 13% is about 1/8, at least approximately). Maybe it would be wiser to try SeaMonkey 2.16 from the nightly builds? I tried Process Explorer, in the Threads section the top one is MSVCR100.dll!_endthreadex+0x80 all the other ones are consuming almost zero cycles If I double-click, I get different stacks, I copied a few, see below, stacks separated by empty lines: ntdll.dll!RtlEnterCriticalSection+0x17 nspr4.dll!PR_Lock+0x17 xul.dll!NS_Free_P+0x2ce157 xul.dll!NS_Free_P+0x2e31ed gkmedias.dll!ogg_stream_clear+0x13f xul.dll!NS_Free_P+0x2e1ffd xul.dll!NS_Free_P+0x2e31ed nspr4.dll!PR_NotifyAll+0x17 xul.dll!NS_Free_P+0x2d938c xul.dll!NS_Free_P+0x2d9445 xul.dll!JSD_GetContextFlags+0x12a0f3 xul.dll!XRE_AddStaticComponent+0x2f32 nspr4.dll!PRP_TryLock+0x49b MSVCR100.dll!_endthreadex+0xe4 kernel32.dll!BaseThreadInitThunk+0x12 ntdll.dll!RtlInitializeExceptionChain+0x63 ntdll.dll!RtlInitializeExceptionChain+0x36 gkmedias.dll!ogg_stream_clear+0x14e xul.dll!NS_InvokeByIndex_P+0x3e398e gkmedias.dll!ogg_stream_clear+0x14e xul.dll!NS_Free_P+0x2e176f xul.dll!NS_Free_P+0x2e30f7 xul.dll!NS_Free_P+0x2d64e1 xul.dll!NS_Free_P+0x2d9312 xul.dll!NS_Free_P+0x2d9445 xul.dll!JSD_GetContextFlags+0x12a0f3 xul.dll!XRE_AddStaticComponent+0x2f32 nspr4.dll!PRP_TryLock+0x49b MSVCR100.dll!_endthreadex+0xe4 kernel32.dll!BaseThreadInitThunk+0x12 ntdll.dll!RtlInitializeExceptionChain+0x63 ntdll.dll!RtlInitializeExceptionChain+0x36 ntdll.dll!RtlCopyMemory+0x1b8 wow64.dll!Wow64EmulateAtlThunk+0x808e wow64.dll!Wow64SystemServiceEx+0xd7 wow64cpu.dll!TurboDispatchJumpAddressEnd+0x2d wow64.dll!Wow64SystemServiceEx+0x1ce wow64.dll!Wow64LdrpInitialize+0x429 ntdll.dll!RtlIsDosDeviceName_U+0x24c87 ntdll.dll!LdrInitializeThunk+0xe ntdll.dll!NtSetInformationFile+0x12 nspr4.dll!PR_Now+0x16d2 xul.dll!NS_Free_P+0x2cd72c xul.dll!NS_Free_P+0x2daa6c xul.dll!NS_Free_P+0x2db951 xul.dll!NS_Free_P+0x2ce157 xul.dll!NS_Free_P+0x2e31ed gkmedias.dll!ogg_stream_clear+0x14e xul.dll!NS_Free_P+0x2e176f xul.dll!NS_Free_P+0x2e30f7 xul.dll!NS_Free_P+0x2d64e1 xul.dll!NS_Free_P+0x2d67d0 xul.dll!NS_Free_P+0x2d940e xul.dll!NS_Free_P+0x2d9445 xul.dll!JSD_GetContextFlags+0x12a0f3 xul.dll!XRE_AddStaticComponent+0x2f32 nspr4.dll!PRP_TryLock+0x49b MSVCR100.dll!_endthreadex+0xe4 kernel32.dll!BaseThreadInitThunk+0x12 ntdll.dll!RtlInitializeExceptionChain+0x63 ntdll.dll!RtlInitializeExceptionChain+0x36
WFM in SM 2.13.1 without flash under Win 7 64bit with 4 Gbyte total RAM. The initial load is slow due to data from yimg.com. How much available RAM has your machine?
URL: http://www.burgerking.de/geschmack-fr...
Flags: needinfo?(lahmbi56789)
My system is a passively cooled i7-3770S nettop, ASUS P8H77-I board, 8 GB RAM, using intel graphics only, there shouldn't be a temperature problem, I'm monitoring the temperatures from time to time, afaict the system has been almost crashfree (apart from a buggy Windows update, which I had to repair manually, known problem, MS had a hotfix for it). I'm using German Win 7 64 bit, don't have much else software installed, I'm using Classic Shell and tweaked the Command Bar in Windows Explorer, removed Windows Media Player, installed SMPlayer, but that shouldn't affect Web browsing. I'm on a (nowadays) relatively slow internet connection, 2 MBit/s, but as I said, in Opera it works for me. I just tested on my old notebook (Windows XP, intel dualcore with ati 1250 xpress chipset, i.e. ati graphics), the page is working there with Seamonkey 2.13.1, bit sluggish, but still ok. So maybe this is an issue with intel drivers. My intel video driver version is 9.17.10.2828, this is the latest driver for that board on ASUS homepage. There are other intel drivers with much 'higher' version numbers, but they refuse to install on my system (something like "no appropriate hardware found".
Flags: needinfo?(lahmbi56789)
Open about:config, set gfx.direct2d.disabled and layers.acceleration.disabled to true, restart browser and see if something change for you
Still the same.
Hi, I tried to play around with some gfx options in about:config, amongst them gfx.prefer-mesa-llvmpipe. Whilst the latter one did not immediately help, I'm quite sure, it somehow changed something, and now the page is working for me too. Turned it off again, and still working. So you may close this somewhat 'exotic' bug.
> gfx.prefer-mesa-llvmpipe I think this is just a coincidence. This only has an effect on Linux and OSX.
Hm, maybe there was something wrong with cached data, anyways, it is working now, so I'm feeling a bit aorry baout the noise.
Closing the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.