REOPENED Bug 44681
[LINUX] Pegs CPU and becomes unusable when trying to play the game at http://tromey.com/Swirl/
https://bugs.webkit.org/show_bug.cgi?id=44681
Summary [LINUX] Pegs CPU and becomes unusable when trying to play the game at http://...
Gustavo Noronha (kov)
Reported 2010-08-26 06:01:35 PDT
I'm filling this on JavaScriptCore, but it seems to be the case with every browser I have available to test here - Epiphany and Firefox go dead, Chromium says the tab is dead. This might be one of those cases in which only one process per tab is a real solution. Here's perf's output: 81.04% ./.libs/libwebkitgtk-3.0.so.0.0.1 GtkLauncher | |--34.20%-- JSC::JSValue::get(JSC::ExecState*, unsigned int) const | |--33.48%-- cti_op_get_by_val | | | --100.00%-- JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&, JSC::JSValue*) | |--20.50%-- JSC::JSArray::getOwnPropertySlot(JSC::ExecState*, unsigned int, JSC::PropertySlot&) | |--8.59%-- cti_op_eq | | | --100.00%-- JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&, JSC::JSValue*) | |--2.66%-- JSC::ObjectPrototype::getOwnPropertySlot(JSC::ExecState*, unsigned int, JSC::PropertySlot&) --0.57%-- [...]
Attachments
Paul Menzel
Comment 1 2010-08-26 07:26:21 PDT
Alexey Proskuryakov
Comment 2 2010-10-09 21:25:16 PDT
Seems to work just fine with ToT on Mac. Server-side change?
Paul Menzel
Comment 3 2010-10-20 03:29:19 PDT
Just as a remark, the plattform is Linux. I cannot change that though. (In reply to comment #2) > Seems to work just fine with ToT on Mac. Server-side change? I am still experiencing this with WebKit 1.2.5-1 in Debian Sid/unstable [1]. [1] http://packages.debian.org/changelogs/pool/main/w/webkit/webkit_1.2.5-1/changelog#versionversion1.2.5-1
Gavin Barraclough
Comment 4 2012-03-26 13:27:58 PDT
Works for me in ToT, can you still reproduce a bug here?
Andy Wingo
Comment 5 2012-05-21 06:26:58 PDT
Works for me with WebKitGTK+ 1.8.1.
Paul Menzel
Comment 6 2012-05-28 10:41:00 PDT
(In reply to comment #5) > Works for me with WebKitGTK+ 1.8.1. Just to make sure. You actually tried the game, by pressing start game and entered some characters into the boxes. (I have not figured the game out yet.) With 1.8.1-3.1 from Debian unstable it still does not work for me. dpkg -l libwebkitgtk-{1,3}.0-0 […] ii libwebkitgtk-1.0-0 1.8.1-3.1 Web content engine library for GTK+ ii libwebkitgtk-3.0-0 1.8.1-3.1 Web content engine library for GTK+ $ LANG=C diff -u /usr/lib/webkitgtk-{1,3}.0-0/libexec/GtkLauncher Binary files /usr/lib/webkitgtk-1.0-0/libexec/GtkLauncher and /usr/lib/webkitgtk-3.0-0/libexec/GtkLauncher differ With `/usr/lib/webkitgtk-1.0-0/libexec/GtkLauncher` it was at 100 % CPU usage more or less after hitting »Start game« and entering a letter in the first box. With `/usr/lib/webkitgtk-3.0-0/libexec/GtkLauncher` it worked some time longer and I was able to insert several letters. But then CPU usage went to 100 % too. So it would be great, if you could reopen this report again, as I am not allowed to do so.
Andy Wingo
Comment 7 2012-05-29 06:52:51 PDT
Hi Paul, I just tried it with the launcher from SVN from today, with run-launcher, as well as with the /usr/lib/webkitgtk-1.0-0/libexec/GtkLauncher from my Debian system: ii libwebkitgtk-1.0-0 1.8.1-1 Web content engine library for GTK+ Everything worked for me. Is there something else I should try? Reopening in the meantime.
Paul Menzel
Comment 8 2012-08-16 03:35:24 PDT
(In reply to comment #7) > Hi Paul, > > I just tried it with the launcher from SVN from today, with run-launcher, as well as with the /usr/lib/webkitgtk-1.0-0/libexec/GtkLauncher from my Debian system: > > ii libwebkitgtk-1.0-0 1.8.1-1 Web content engine library for GTK+ > > Everything worked for me. Is there something else I should try? > > Reopening in the meantime. Thanks and sorry for the late reply. The page loasds fine. Clicking on »Start Game« still shows no problem. But clicking with the cursor in the first empty box, then I see the 100 % CPU usage.
Note You need to log in before you can comment on or make changes to this bug.