Closed Bug 271171 Opened 20 years ago Closed 19 years ago

firefox often crashes when opening pages with mozilla-xremote-client

Categories

(Firefox :: Tabbed Browser, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: cs, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 StumbleUpon/1.999
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 StumbleUpon/1.999

I routinely open new web pages with mozilla-xremote-client.
Increasingly (as of firefox-1.0) this results in a crash with a
segmentation violation.
It's not specific to a particular page, nor 100% reliable.


Reproducible: Sometimes
Steps to Reproduce:
The easiest way to reproduce this is to queue up a lot (eg 20 or so)
calls to mozilla-xremote-client is quick succession. If I do that
I am close to certain to have the browser fall over.

Notably, it's not the opening of the tabs themselves; if I use the magpie
extension to highlight lots of links and go "open all in tabs" then I get
lots of tabs quite happily.

So I'm imagining some race condition in the xremote stuff.

Actual Results:  
Browser crashes with segmentation violation.


Expected Results:  
Opened a new window or tab.
I have correlated this somewhat with some GTK/X11 font weirdness.

I have a laptop on which firefox is very very stable, and my gtkrc fonts
are honoured. I have a desktop where the Gnome stuff is finding some
ludicrously large fonts to use. My menus are Very Fat, and many web page
components are also very strange - large fonts, typically in form elements
rather than HTML body text. Many items are not rendered correctly, much as
though the browser is expecting or being told the font is one size and the
lower layers are rendering with another - sometimes text overflows its box,
etc.

Anyway, it's not tied to the browser, it's tied to the display.
I can fire up either browser on either display and those shown
on the laptop look right and are quite stable, which those shown
on the desktop look very ugly and crash easily.

I have yet to find the salient difference, since both machines
are quite recent Fedora Core 3 installs and appear to have the
same font packages and X11 server software. However, it would be
useful perhaps to see if there's opportunity in the browser rendering
stuff to ask for a font and proceed (incorrectly) in the belief we
were given what we expect. Certainly some layout effect look like
disagreement between rendered text sizes and the sizes used to place
other stuff around it.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.