forgot browser version:
7.0.547.0 (61463) Ubuntu 10.10

i've launched a new profile and got no crash
but it had this
[768:783:33156902305:ERROR:net/disk_cache/backend_impl.cc(1193)] Critical error found -8

nocrash 3.4 KB View Download

Thanks for the bug report, but I don't think you're going to get anyone to fix a crash that happens on an alpha quality version of Chrome running on a Linux distro that's a currently a work in progress, and only with your profile.

Given that, if you make a copy of your bad profile and put it in /tmp/badprofile, then try builds older than r61463 from http://build.chromium.org/buildbot/continuous/linux64/, with --user-data-dir=/tmp/badprofile, can you reproduce the bug? If you can narrow it down to a particular change or range of changes that cause this problem, maybe we can help fix it.

Someone reported reproducible crashes on identica with the same dbus messages in the terminal, using the latest chromium stable (6.0.472.63):

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/655932

not sure it's the same bug though.

I think this should be fixed in Chrome 9?

I believe so, Lei.

Chrome Version       : <Copy from: 'about:version'>
URLs (if applicable) : http://brainbird.net/search/people
Other browsers tested:
  Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12pre) Gecko/20101005 Ubuntu/10.10 (maverick) Namoroka/3.6.12pre: OK


What steps will reproduce the problem?
1. clicked on Search link


What is the expected result?
open search page

What happens instead?
crashed

Please provide any additional information below. Attach a screenshot if
possible.
process 14175: arguments to dbus_pending_call_free_data_slot() were incorrect, assertion "*slot_p >= 0" failed in file dbus-pending-call.c line 748.
This is normally a bug in some application using the D-Bus library.
process 14175: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application called unref() too many times and removed a reference belonging to libdbus, since this is a shared connection.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd945e710 (LWP 29535)]
SLL_PopRange (this=0x7ffff8722600, src=0x7ffff87226a8, cl=<value optimized out>, N=8) at third_party/tcmalloc/chromium/src/linked_list.h:73
73	third_party/tcmalloc/chromium/src/linked_list.h: No such file or directory.
	in third_party/tcmalloc/chromium/src/linked_list.h
(gdb) thread apply all bt

Chrome Version       : <Copy from: 'about:version'>
URLs (if applicable) : http://brainbird.net/search/people
Other browsers tested:
  Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12pre) Gecko/20101005 Ubuntu/10.10 (maverick) Namoroka/3.6.12pre: OK


What steps will reproduce the problem?
1. clicked on Search link


What is the expected result?
open search page

What happens instead?
crashed

Please provide any additional information below. Attach a screenshot if
possible.
process 14175: arguments to dbus_pending_call_free_data_slot() were incorrect, assertion "*slot_p >= 0" failed in file dbus-pending-call.c line 748.
This is normally a bug in some application using the D-Bus library.
process 14175: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application called unref() too many times and removed a reference belonging to libdbus, since this is a shared connection.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd945e710 (LWP 29535)]
SLL_PopRange (this=0x7ffff8722600, src=0x7ffff87226a8, cl=<value optimized out>, N=8) at third_party/tcmalloc/chromium/src/linked_list.h:73
73	third_party/tcmalloc/chromium/src/linked_list.h: No such file or directory.
	in third_party/tcmalloc/chromium/src/linked_list.h
(gdb) thread apply all bt

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.