On Tue, Nov 15, 2011 at 05:18:23PM +0100, Mike Hommey wrote: > On Tue, Nov 15, 2011 at 03:23:18PM +0100, Sebastian Reichel wrote: > > On Tue, Nov 15, 2011 at 02:46:37PM +0100, Mike Hommey wrote: > > > On Tue, Nov 15, 2011 at 01:45:29PM +0100, Sebastian Reichel wrote: > > > > Package: libnss3-1d > > > > Version: 3.13.1.with.ckbi.1.88-1 > > > > Severity: critical > > > > > > > > Hi, > > > > > > > > This release breaks chromium 14 from Debian testing. It crashes > > > > with the same symptoms described in Debian Bug #647992 [0]. > > > > Installing libnss3-1d from testing (3.12.11-3) fixes the issue. > > > > > > > > [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647992 > > > > > > I doesn't crash here. Can you get a backtrace? > > > > (gdb) bt > > #0 0x0000000000000000 in ?? () > > #1 0x00007ffff5e62491 in BalloonViewHost::UpdateActualSize > > (this=0x7ffff942fb60, new_size=...) at > > chrome/browser/ui/gtk/notifications/balloon_view_host_gtk.cc:22 > > #2 0x00007ffff5e62241 in BalloonViewImpl::AnimationProgressed > > (this=0x7ffff8d54d00, animation=0x7ffff891a200) at > > chrome/browser/ui/gtk/notifications/balloon_view_gtk.cc:205 > > #3 0x00007ffff618cde7 in ui::LinearAnimation::Step (this=0x7ffff891a200, > > time_now=<optimized out>) at ui/base/animation/linear_animation.cc:76 > > #4 0x00007ffff618cac5 in ui::AnimationContainer::Run (this=0x7ffff857dde0) > > at ui/base/animation/animation_container.cc:76 > > #5 0x00007ffff60aeaae in (anonymous namespace)::TaskClosureAdapter::Run > > (this=0x7ffff92f3b60) at base/message_loop.cc:104 > > #6 0x00007ffff60af506 in Run (this=0x7fffffffb5f0) at ./base/callback.h:265 > > #7 MessageLoop::RunTask (this=0x7ffff83c6c00, pending_task=...) at > > base/message_loop.cc:484 > > #8 0x00007ffff60b3aa3 in MessageLoop::DeferOrRunPendingTask > > (this=0x7ffff83c6c00, pending_task=...) at base/message_loop.cc:502 > > #9 0x00007ffff60b3e5d in DoDelayedWork > > (next_delayed_work_time=0x7ffff839e720, this=0x7ffff83c6c00) at > > base/message_loop.cc:731 > > #10 MessageLoop::DoDelayedWork (this=0x7ffff83c6c00, > > next_delayed_work_time=0x7ffff839e720) at base/message_loop.cc:703 > > #11 0x00007ffff60e60f2 in base::MessagePumpGlib::RunWithDispatcher > > (this=0x7ffff839e700, delegate=<optimized out>, dispatcher=<optimized out>) > > at base/message_pump_glib.cc:215 > > #12 0x00007ffff60b2ce5 in MessageLoop::RunInternal (this=0x7ffff83c6c00) at > > base/message_loop.cc:451 > > #13 0x00007ffff60b2dcc in RunHandler (this=<optimized out>) at > > base/message_loop.cc:424 > > #14 MessageLoopForUI::Run (this=<optimized out>, dispatcher=<optimized > > out>) at base/message_loop.cc:834 > > #15 0x00007ffff57cb112 in RunUIMessageLoop (browser_process=<optimized > > out>) at chrome/browser/browser_main.cc:708 > > #16 BrowserMain (parameters=...) at chrome/browser/browser_main.cc:2070 > > #17 0x00007ffff57baee9 in RunNamedProcessTypeMain > > (main_function_params=..., process_type=...) at > > chrome/app/chrome_main.cc:552 > > #18 ChromeMain (argc=<optimized out>, argv=<optimized out>) at > > chrome/app/chrome_main.cc:895 > > #19 0x00007ffff57bbc09 in main (argc=2, argv=0x7fffffffe438) at > > chrome/app/chrome_exe_main_gtk.cc:46 > > I fail to see where nss is supposed to be involved, here...
Probably the crash is a side effect, so NSS is not involved in the backtrace. I can reproduce this bug as follows: chromium | libnss3-1d | status --------------------------------------------------------- 14.0.835.202~r103287-1 | 3.12.11-3 | OK 14.0.835.202~r103287-1 | 3.13.1.with.ckbi.1.88-1 | Crash 15.0.874.106~r107270-1 | 3.12.11-3 | Crash 15.0.874.106~r107270-1 | 3.13.1.with.ckbi.1.88-1 | Crash I guess the actual bug is in chromium, but if libnss3-1d transitions into testing chromium will be unusable. So I suggest to leave this open until chromium is fixed. -- Sebastian
signature.asc
Description: Digital signature
