Comment #1 on issue 32061 by Robert.Bradbury: Restoring session can make
browser completely nonfunctional
http://code.google.com/p/chromium/issues/detail?id=32061
I'm fairly sure dbg1.trc is a stack trace I mentioned of the main process
at the
point at which everything hangs (the trace file has been edited somewhat to
remove
non-relevant parts of the gdb session. I believe I may have the saved
critical
elements of this session and could be able to test recreating it (I don't
yet know
how to create an alternate chromium session (profile) under the same user
id but am
not enthusiastic to interfere with the currently restored session, even
without
Javascript or Flash -- it isn't unusual for me to run single sessions for
weeks so
long as they are performing efficiently -- in part because restoring
complex sessions
takes such a long time).
I'm assuming that channel 14 in dbg1.trc may be the channel between the
process and
the X server but am not sure.
ps.hung.family shows the process status (ignore the root chrome instance,
the
bradbury instance is the one with the restart problem).
An attempt somewhat earlier in the day to strace the activity of the "hung"
session
yielded the following:
Process 24846 attached - interrupt to quit
write(14, "!", 1 <unfinished ...>
Process 24846 detached
On the other hand a strace on a normal "simple" chrome process (gmail and
this issue
(#32061) being the only open tabs), e.g. normal.trc, yields a complex
mixture of
inotify_add_watch, gettimeofday, poll and an occasional read or write calls
-- but it
is definitely not "hung".
Attachments:
dbg1.trc 79.4 KB
ps.hung.family 12.7 KB
normal.trc 2.6 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
