Comment #5 on issue 26016 by duncan.lock: Complete chromium crash loading
hacks.mozilla.org/2009/10/font-control-for-designers/
http://code.google.com/p/chromium/issues/detail?id=26016
Ok, I looked back in my history file and I'd fat fingered an extra dash
into the --user-data-dir
command earlier, so I've got that working now. It still crashes using a new
profile via --user-data-
dir though. I then tried to capture a debugging trace using GDB following
the instructions pointed to
in comment 1.
This seems to work, but when running under GDB it doesn't crash when you
load that page, it appears
to hang. I've never used GDB before, so I'm not sure if this is what it's
supposed to do, or what.
It says 'Segmentation Fault' at the right place in the GDB output, same as
it does in the console, so
I assume this is reproducing the crash.
Anyway, following the instructions, I've captured two traces:
gdb-chromium1.txt is run normally, with
just '--user-data-dir=/home/duncan/.config/google-chrome/test
--enable-plugins' as parameters. gdb-
chromium4.txt is run single process with these
parameters: '--single-process --enable-plugins --user-
data-dir=/home/duncan/.config/google-chrome/test'. Hope this is useful, but
let me know if there's
anything wrong with these, or anything else I could add that would help.
Attachments:
gdb-chromium1.txt 35.9 KB
gdb-chromium5.txt 39.5 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
-~----------~----~----~----~------~----~------~--~---
