On Fri, Feb 03, 2012 at 09:00:36AM +0100, Luc Maisonobe wrote:
> Le 02/02/2012 23:10, Mike Hommey a écrit :
> > On Thu, Feb 02, 2012 at 07:58:41PM +0100, Luc Maisonobe wrote:
> >> Le 01/02/2012 11:00, Luc Maisonobe a écrit :
> >>> Le 01/02/2012 10:37, Mike Hommey a écrit :
> >>>> On Wed, Feb 01, 2012 at 09:58:28AM +0100, Luc Maisonobe wrote:
> >>>>> Le 31/01/2012 12:19, Mike Hommey a écrit :
> >>>>>> On Mon, Jan 30, 2012 at 10:22:44PM +0100, Luc Maisonobe wrote:
> >>>>>>> Hello,
> >>>>>>>
> >>>>>>> I confirm the same freeze occurs here, also since around christmas.
> >>>>>>> Looking into xsessions-errors, I get different messages. The one that
> >>>>>>> may help you is:
> >>>>>>>
> >>>>>>> /usr/lib/xulrunner-9.0/plugin-container: symbol lookup error:
> >>>>>>> /usr/lib/xulrunner-9.0/plugin-container: undefined symbol:
> >>>>>>> XRE_InitChildProcess
> >>>>>>>
> >>>>>>> It is repeated several time. The freeze seems to occur when some
> >>>>>>> scripts
> >>>>>>> are in the page, I also got messages saying a script on a page never
> >>>>>>> ended.
> >>>>>>> It also seems after a freeze with several open tabs, the system
> >>>>>>> monitoring shows up several zombie plugin-containers processes. I was
> >>>>>>> not able to identify which plugin.
> >>>>>>
> >>>>>> Can you try iceweasel 10 from experimental? It may be fixed there.
> >>>>>
> >>>>> I tried to install it but after the add-ons compatibility checking
> >>>>> (which succeeded), it failed at startup with a popup window displaying a
> >>>>> message along the following lines (I translate the message from French):
> >>>>>
> >>>>> XML analysis error: undefined entity
> >>>>> Location: chrome://browser/content/browser.xul
> >>>>> Line number 553, column 7:
> >>>>> <menuitem id="content-videa-showstats"
> >>>>> ------^
> >>>>>
> >>>>> The main window never appeared after this error popup.
> >>>>
> >>>> Did you upgrade iceweasel-l10n-fr ?
> >>>
> >>> No, I forgot to update it. Sorry for that.
> >>>
> >>> I have now successfully installed inceweasel 10 and started to use it.
> >>> No hang for the first few seconds of used (I tried to open a lot of tabs
> >>> to stress it a little). I'll update the issue if I see some changes.
> >>
> >> After somes tests, it seems the problem is still there with iceweasel
> >> 10. Running strace on a stuck browser shows the same pattern as before,
> >> a very long timeout on a call:
> >>
> >> futex(0x7ff2051c608c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1,
> >> {1328209105, 697780000}, ffffffff
> >
> > Do you still see the undefined symbol error? If so, can you try
> > iceweasel 11 from mozilla.debian.net (currently iceweasel-aurora, but if
> > you wait enough, it will be in experimental)
>
> No, the undefined symbol seems to have been corrected with version 10,
> thanks. So I guess the freeze and the symbol were unrelated problems.
> The freeze still occurs.
>
> Another point I forgot to mention. When the freeze occurs, really
> everything is stopped on the browser window, including the small
> rotating ring animation in the tabs. Also when the freeze occurs when a
> context menu (right click) is open, this menu also freeze and in fact in
> this case it seems to me the complete window manager is frozen (in gnome
> shell, the stripe at the left of the screen does not appear anymore when
> hovering the mouse around left corner). I am not a GUI expert, but it
> seems the freeze is somewhere inside the GUI events and rendering loop.
> When a context menu is displayed, this loop grab the focus for the whole
> display so no event can reach other windows.
>
> Is there something I could do to try to dump X events while the freeze
> occurs to help developers understand the problem ? Perhaps something in
> the spirit of the strace command I used to trace down system calls, but
> this time focusing on window events ?
When it's frozen, is there a plugin-container process running?
Mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
