Status: Unconfirmed Owner: ---- Labels: OS-Linux Area-Misc Size-Medium Type-Bug
New issue 18198 by [email protected]: parent chrome process eating 100% CPU indefinitely (AFAICT) http://code.google.com/p/chromium/issues/detail?id=18198 Chrome Version : 3.0.196.0 OS + version : ubuntu hardy CPU architecture (32-bit / 64-bit): 64-bit window manager : gnome URLs (if applicable) : Behavior in Firefox 3.x (if applicable): Behavior in Chrome for Windows (optional): What steps will reproduce the problem? Unknown, sorry. What is the expected result? N/A What happens instead? Parent chrome process seems to be eating 100% CPU. This continued until I killed it, after at least 30 minutes looking into it (strace, gdb, etc). This may be a rare issue, so I'm reporting it, even though I have not verified this against nightly builds, etc. Please provide any additional information below. Attach a screenshot and backtrace if possible. top says: 22307 epizzi 20 0 258m 112m 19m S 96 3.7 3606:56 chrome ps auxfww shows this to be the parent process: epizzi 22307 24.8 3.7 264772 115164 ? Sl Jul21 3607:09 /opt/google/chrome/chrome epizzi 22330 0.0 0.0 115684 2652 ? S Jul21 0:10 \_ /opt/google/chrome/chrome epizzi 22336 0.0 0.1 60348 4796 ? S Jul21 0:00 \_ /opt/google/chrome/chrome --type=zygote root 22337 0.0 0.0 0 0 ? Z Jul21 0:00 | \_ [chrome-sandbox] <defunct> epizzi 18312 0.0 0.6 108928 20232 ? Sl Jul21 0:03 | \_ /opt/google/chrome/chrome --type=zygote epizzi 29866 0.0 0.6 109916 19624 ? Sl Jul21 0:06 | \_ /opt/google/chrome/chrome --type=zygote epizzi 7515 0.0 0.6 105136 19872 ? Sl Jul22 0:05 | \_ /opt/google/chrome/chrome --type=zygote epizzi 10928 0.0 0.4 99096 14264 ? Sl Jul22 0:03 | \_ /opt/google/chrome/chrome --type=zygote epizzi 28661 1.0 6.6 262428 205984 ? Sl Jul24 98:50 | \_ /opt/google/chrome/chrome --type=zygote epizzi 19532 0.6 3.3 157476 102792 ? Sl Jul24 61:24 | \_ /opt/google/chrome/chrome --type=zygote epizzi 1136 0.4 2.0 121896 64328 ? Sl Jul29 13:20 | \_ /opt/google/chrome/chrome --type=zygote epizzi 6379 0.0 1.1 112996 35392 ? Sl Jul30 0:05 | \_ /opt/google/chrome/chrome --type=zygote epizzi 30593 1.3 1.1 108088 35760 ? Sl 12:51 0:03 | \_ /opt/google/chrome/chrome --type=zygote epizzi 22427 0.0 0.0 0 0 ? Z Jul21 0:00 \_ [chrome] <defunct> epizzi 24246 0.0 0.0 0 0 ? Z Jul21 0:00 \_ [chrome] <defunct> epizzi 25666 0.0 0.0 0 0 ? Z Jul21 0:00 \_ [chrome] <defunct> epizzi 27014 0.0 0.0 0 0 ? Z Jul21 0:00 \_ [chrome] <defunct> epizzi 31110 0.0 0.0 0 0 ? Z Jul22 0:00 \_ [chrome] <defunct> epizzi 31602 0.0 0.0 0 0 ? Z Jul22 0:00 \_ [chrome] <defunct> epizzi 12745 0.0 0.0 0 0 ? Z Jul22 0:00 \_ [chrome] <defunct> epizzi 24926 0.0 0.0 0 0 ? Z Jul22 0:00 \_ [chrome] <defunct> epizzi 27229 0.0 0.0 0 0 ? Z Jul22 0:00 \_ [chrome] <defunct> epizzi 30759 0.0 0.0 52356 1856 ? Sl Jul23 0:00 \_ /opt/google/chrome/chrome --type=utility -- channel=22307.efdccc58.1848277418 GDB backtrace: $ gdb -p 22307 ... Attaching to process 22307 Reading symbols from /opt/google/chrome/chrome... WARNING: no debugging symbols found in /opt/google/chrome/chrome. ... Cannot access memory at address 0x1b93ea ... (gdb) bt #0 0xffffe410 in ?? () #1 0xffec8e48 in ?? () #2 0x00000143 in ?? () #3 0x00000007 in ?? () #4 0xf7344d87 in ?? () #5 0x00000000 in ?? () Strace output attached as well. Attachments: trace 44.9 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
