Comment #6 on issue 17179 by gouedard: Freeze for 15s when opening option
dialog box
http://code.google.com/p/chromium/issues/detail?id=17179
As I am not a programming guru, I couldn't tell if outputs I get were
useful or not.
I then attached all of them in case it helps...
I tried what you suggested (it still occurs when using an empty profile).
Once
google chrome started, with only one tab (about:linux-splash), I grep-ed
for chorme
in ps. Here are the pids and the states of the processes at that point :
6179 Sl+ /opt/google/chrome/chrome
6191 S+ /opt/google/chrome/chrome
6192 S+ /opt/google/chrome/chrome --type=zygote
6193 Sl+ /opt/google/chrome/chrome --type=zygote
I then started the strace and open the options. As soon as clicking on the
option
form the menu, the strace abort (see output below). I tried several times
and it
always acts the same. After ~15s, the option dialog box opens (but strace
already
aborted at that time).
>> strace -p 6179 -p 6191 -p 6192 -p 6193 -tt -f 2>strace_chrome
[ Process PID=6194 runs in 32 bit mode. ]
[ Process PID=6635 runs in 64 bit mode. ]
*** glibc detected *** strace: corrupted double-linked list:
0x000000000111e420 ***
======= Backtrace: =========
/lib/libc.so.6[0x7f5530e01cb8]
/lib/libc.so.6[0x7f5530e0402e]
/lib/libc.so.6[0x7f5530e05db7]
/lib/libc.so.6(realloc+0x12e)[0x7f5530e06dae]
strace[0x402a3b]
strace[0x411235]
strace[0x4057d5]
strace[0x404916]
/lib/libc.so.6(__libc_start_main+0xe6)[0x7f5530da85a6]
strace[0x402119]
======= Memory map: ========
00400000-00447000 r-xp 00000000 08:06 115603
/usr/bin/strace
00646000-00647000 r--p 00046000 08:06 115603
/usr/bin/strace
00647000-00648000 rw-p 00047000 08:06 115603
/usr/bin/strace
00648000-00656000 rw-p 00648000 00:00 0
0111d000-0113e000 rw-p 0111d000 00:00 0
[heap]
7f552c000000-7f552c021000 rw-p 7f552c000000 00:00 0
7f552c021000-7f5530000000 ---p 7f552c021000 00:00 0
7f5530b72000-7f5530b88000 r-xp 00000000 08:06 548996
/lib/libgcc_s.so.1
7f5530b88000-7f5530d88000 ---p 00016000 08:06 548996
/lib/libgcc_s.so.1
7f5530d88000-7f5530d89000 r--p 00016000 08:06 548996
/lib/libgcc_s.so.1
7f5530d89000-7f5530d8a000 rw-p 00017000 08:06 548996
/lib/libgcc_s.so.1
7f5530d8a000-7f5530ef2000 r-xp 00000000 08:06 549175
/lib/libc-2.9.so
7f5530ef2000-7f55310f2000 ---p 00168000 08:06 549175
/lib/libc-2.9.so
7f55310f2000-7f55310f6000 r--p 00168000 08:06 549175
/lib/libc-2.9.so
7f55310f6000-7f55310f7000 rw-p 0016c000 08:06 549175
/lib/libc-2.9.so
7f55310f7000-7f55310fc000 rw-p 7f55310f7000 00:00 0
7f55310fc000-7f553111c000 r-xp 00000000 08:06 548902
/lib/ld-2.9.so
7f55312f3000-7f55312f5000 rw-p 7f55312f3000 00:00 0
7f5531317000-7f553131b000 rw-p 7f5531317000 00:00 0
7f553131b000-7f553131c000 r--p 0001f000 08:06 548902
/lib/ld-2.9.so
7f553131c000-7f553131d000 rw-p 00020000 08:06 548902
/lib/ld-2.9.so
7fff39308000-7fff3931d000 rw-p 7ffffffea000 00:00 0
[stack]
7fff393ff000-7fff39400000 r-xp 7fff393ff000 00:00 0
[vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0
[vsyscall]
Aborted
I also tried to strace the processes one by one, but the strace with the
first
process (6179) terminates with a segmentation fault as soon as I put the
mouse over
the google-chrome window... I attached the result of "strace -p 6179 -tt -f
2>strace_chrome_6179" in case it helps (I made a mistake and in this file
the pid of
the process is 7307 and not 6179 because I re-do it and overwrite the
strace_chrome_6179 file)...
I finally tried to strace all-but-the-first processes, which pids are now
7687,7688,7689. With this last try I was able to open the option dialog
box (again,
after 15s), and ^C the strace afterward. I attached the corresponding
strace called
strace_chrome_allButFirst.
Attachments:
strace_chrome.gz 1.7 MB
strace_chrome_6179.gz 2.1 KB
strace_chrome_allButFirst.gz 20.4 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
-~----------~----~----~----~------~----~------~--~---
