Closed Bug 183467 Opened 22 years ago Closed 22 years ago

Browser freezes when used (Redhat 8.0 xft enabled RPM's).

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: meherenow, Assigned: blizzard)

References

Details

(Keywords: hang)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202

I have a fresh install of Redhat 8 that I applied the xft enabled rpms to, the
browser itself looks great however I am finding it un-usable in that it just
freezes upon loading almost any url. On the odd occasion it does not freeze,
refreshing the page will cause the browser to lock up.

Reproducible: Always

Steps to Reproduce:
1. Start mozilla
2. Attempt to visit a url (a variety tried, including http://www.google.com)
3. Browser locks up.

Actual Results:  
Browser locks up, page is not displayed.

Expected Results:  
Browser should download and display page.

I have a similar machine, allbeit with less memory and a slower processor
running RH8 with the same rpm's and am not experiencing the same problem on that
machine.

Both machines have fresh installs, neither have any form of plugin loaded.

I'll attach an strace of the crash/freeze.
> I'll attach an strace of the crash/freeze.

a stacktrace from gdb would probably be more useful
does the same behavior exist if you use a non-xft build?
Keywords: hang
-> XFT master
Assignee: asa → blizzard
Yeah, I need a stack trace because it's working just fine here.
Blocks: xft_tracking
After toying around with my second machine at work I became convinced that it
must be a hardware with my home machine.

I've tweaked back some of the settings in the bios, and lo and behold, it
behaves itself.

Apologies for taking up your time, but you're all doing a great job with Mozilla.

Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.