[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Firefox crashes

This page also crashes FF running on disklessworkstation.com's LTSP Term 1225e

Running the mozilla debugger options produces this at the point of crash:

The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
 (Details: serial 145503 error_code 11 request_code 53 minor_code 0)
 (Note to programmers: normally, X errors are reported asynchronously;
  that is, you will receive the error a while after causing it.
  To debug your program, run it with the --sync command line
  option to change this behavior. You can then get a meaningful
  backtrace from your debugger if you break on the gdk_x_error() function.)

Program exited with code 01.

I don't understand - would this problem really be remedied by having more RAM? My i810 boxes that exhibited the same crash all had more than 64MB memory (One had 384). On the other end of this is the 1225 terminal, which has 16MB videoram (specified in lts.conf) and 128MB total.

I can't imagine that this crash is pervasive; no one would be using LTSP if it were. I'm wondering what it is about my specific location (And those whom are also affected) that is causing this to occur so often and repeatably.

- Michael Blinn

informatik steinerschule-basel ch wrote:
es könnte auch sein, daß eventuell zwei miteinander unverträgliche Speichermodule eingebaut sind.

Oder das Java Plugin wurde nicht korrekt installiert. Damit das plugin funktioniertdarf nur eine Verknüpfung zum Plugin ins Zielverzeichnis kopiert werden. Wir benutzen bei uns im Celeron 400 PC auch 128 MB RAM.

Ich glaube nicht, daß es am RAM liegt.
This gives more evidence, that firefox may easily crash a low memory (64MB) xserver: "The problem may be related to some programs caching things like bitmaps in the x-server. Can you see a relation to the programs you are using and the amount of memory X is using?"

The example page given below is a good test case because firefox has to load big image files (e.g. 2592x1944) which are downscaled to 350x230. - If firefox does cache bitmaps in the X-Server it would obviously need additional RAM on the LSTP client.

On my laptop (not ltsp) Xorg takes another 10 MB RAM when opening section "Bilder" on alp-tschingla.ch.




Von: informatik steinerschule-basel ch
An: "Support list for open source software in schools." <k12osn redhat com>
Betreff: Re: [K12OSN] Firefox crashes
Datum: Mon, 11 Jun 2007 14:38:35 +0200

> I've got zero problems with the page. I'm on firefox k12ltsp 6
> and I did it with both a via and i810 chipset. I didn't see it in
> previous posts (forgive me if I overlooked it) but
> how much memory do your clients have? What screen resolution are you
> running?
> 800x600 generally needs at least 64mb of ram
> 1024x768 will need 128mb to browse a variety of javascript and flash
> sites.
> My clients had at least 128mb.
> regards,
> William
I can confirm that: k12ltsp 6, firefox 1.5, 1280x1024x15 screen, booted
from pxe
(and same behaviour with firefox 2 on k12ltsp 7).

With 64 MB RAM even a page just with images crashes firefox
(<a href=http://www.alp-tschingla.ch,>http://www.alp-tschingla.ch,</a>open
section "Bilder").

With 128 MB RAM the same page works.

So maybe the hardware requirements for the clients should be updated
because nowadays many people use a screen resolution bigger than
800x600 pixels.


K12OSN mailing list
K12OSN redhat com
For more info see <http://www.k12os.org>


This message, and any attachments that may accompany it, contain information that is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise exempt from disclosure under applicable law. If the recipient of this message is not the intended recipient, any disclosure, copying, or other use of this communication or any of the information, which it contains is unauthorized and prohibited. If you have received this message in error, please notify the original sender by return mail and delete this message, along with any attachments, from your computer. Thank you.
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]