Mailinglist Archive: opensuse-bugs (15100 mails)

< Previous Next >
[Bug 326132] New: firefox on ia64 unresponsive when you click on 'content' in preferences
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 18 Sep 2007 12:36:48 -0600 (MDT)
  • Message-id: <bug-326132-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=326132

           Summary: firefox on ia64 unresponsive when you click on 'content'
                    in preferences
           Product: openSUSE 10.3
           Version: Beta 3
          Platform: Other
        OS/Version: openSUSE 10.3
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Firefox
        AssignedTo: bnc-team-mozilla@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: erikj@xxxxxxx
         QAContact: qa@xxxxxxx
          Found By: Third Party Developer/Partner


Created an attachment (id=173142)
 --> (https://bugzilla.novell.com/attachment.cgi?id=173142)
gdb info (probably not too helpful)

Firefox becomes unresponsive when you try to click on 'content' in prefs

This was observed in opensuse 10.3 beta3 on unofficial ia64 bits.

When firefox is started, it appears to work fine.

Then I decided to change some preferences.

I navigated:
edit -> Preferences -> content (icon with the globe at the top)

When I went to content, firefox become unresponsive.

** this is repeatable **

My desktop is gnome if it matters.

It appears to work fine with 'main', 'tabs.  'Privacy' has a problem and
I'll file it separately (but ok if it's duped).

I connected gdb to the firefox pid:

I'm not sure the details there are useful, but I'll attach what I have.

Connecting with strace shows it's waiting for a lcok some how:

hoot:/var/log # strace -p 30970
Process 30970 attached - interrupt to quit
futex(0x20000000020ddd20, FUTEX_WAIT, 2, NULL



Firefox version from rpm is:
MozillaFirefox-2.0.0.6-9


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >