Only on LTSP clients. Direct on the desktop works.
De: David Groos
Enviado: sexta-feira, 30 de dezembro de 2016 11:27:55
Para: ltsp-discuss@lists.sourceforge.net
Assunto: Re: [Ltsp-discuss] firefox crashes
I also don't have this problem. I'm using f
Daemon A wrote:
> Only works with firefox downgrade.
>
> 3 months with the same problem.
>
> --
> *De:* Alkis Georgopoulos
> *Enviado:* segunda-feira, 19 de dezembro de 2016 02:13:16
> *Para:* ltsp-discuss@lists.sourceforge.net
> *Assunto:* Re: [
Only works with firefox downgrade.
3 months with the same problem.
De: Alkis Georgopoulos
Enviado: segunda-feira, 19 de dezembro de 2016 02:13:16
Para: ltsp-discuss@lists.sourceforge.net
Assunto: Re: [Ltsp-discuss] firefox crashes
On 18/12/2016 08:06 ??, Daemon
On 18/12/2016 08:06 μμ, Daemon A wrote:
>
> From the latest firefox updates, it crashes in ltsp.
>
> I already tested ubuntu desktop 14 and ubuntu desktop 16. Firefox
> crashes all
>
>
It works fine for me on Ubuntu 16.04 with firefox
50.1.0+build2-0ubuntu0.16.04.
Tested a fat client and a thin
>From the latest firefox updates, it crashes in ltsp.
I already tested ubuntu desktop 14 and ubuntu desktop 16. Firefox crashes all
--
Check out the vibrant tech community on one of the world's most
engaging tech sites,
Does the setting browser.cache.disk.capacity at all affect this issue?
If we turned the Firefox cache way down, then why wouldn't that limit
the amount of stuff that FF sends to the XServer to store?
-Michael
Jim Kronebusch wrote:
plus, i'll open a new bugzilla with ff about the pixmap issue o
Do you recall what the code for 4.2 was ? I have yet to make the leap to
LTSP5
-Michael
Ondrej Valousek wrote:
The problem is in FF consuming all available memory on the client for
pixmaps.
In LTSP 4.2 X startup scripts there was a code that limited the X server
memory to what was actually acc
> Firefox would crash before it gets a chance to display anything. Maybe
> we could say that "no single app can allocate more than 75% of ram", and
> then *hope* that they all play nice.
>
>
That's exactly what I wanted to do - limit a single app to say 75% of ram.
> I think if app developer
> I 100% agree with Jim but I however do not 100% agree with the bug
> subject he referenced.
> Bottom line is that Xorg does not currently have a way to limit its RAM
> demands, but we do have a perfectly working solution for this - so why
> should the X developers waste their time implementing so
Ondrej Valousek wrote:
>> There's already a bug on this. I opened it a couple of years ago.
>>
>>https://bugs.freedesktop.org/show_bug.cgi?id=4942
>>
>> But, what's the Xserver to do? Deny allocating any ram to the Xclient?
>> that's what the XRAMPERC does.
>>
>
> I 100% agree with J
> There's already a bug on this. I opened it a couple of years ago.
>
>https://bugs.freedesktop.org/show_bug.cgi?id=4942
>
> But, what's the Xserver to do? Deny allocating any ram to the Xclient?
> that's what the XRAMPERC does.
>
I 100% agree with Jim but I however do not 100% agree
On Thu, 06 Sep 2007 16:27:44 +0200, Ondrej Valousek wrote
> Hi Scott,
>
> Nice work! In the mean time, we need to add the code:
Ondrej, check out the post I forwarded to the list a few minutes ago. It is a
step by
step to modify an Edubuntu installation to accept the new XRAMPERC= variable in
> plus, i'll open a new bugzilla with ff about the pixmap issue or check
> the status of
> the current x-carsh-pixmaps bug (if one present ?)
I opened the following two bugs today, one with Ubuntu in Launchpad and the
other with
Mozilla in bugzilla to address this:
https://bugs.launchpad.net/ubu
Nadav Kavalerchik wrote:
> i think i solved it with all of your helpful advices! , thanks you :-)
>
> the script that Ondrej suggested i use was already in startx but was
> never used by me.
> so i set the XRAMPERC to 80 and found out that when i overload FF with
> 20 tabs that hold flash object
i think i solved it with all of your helpful advices! , thanks you :-)
the script that Ondrej suggested i use was already in startx but was
never used by me.
so i set the XRAMPERC to 80 and found out that when i overload FF with
20 tabs that hold flash objects and heavy graphics the FF crashes
alo
thank you for the responses :-)
i'm using fc6 with ltsp 4.2 so i'll check and see if the X-anti-crash
script is in place
and if not add it.
plus, i'll open a new bugzilla with ff about the pixmap issue or check
the status of
the current x-carsh-pixmaps bug (if one present ?)
we try to use opera
Ondrej Valousek wrote:
> Talking about screen.d scripts... in the mean time, would it be possible
> for Gutsy to contain some more interesting things? Like ssh or startnx
> scripts. I can provide them if anyone is interested...
We're past UVF in gutsy, so it'd have to wait for gutsy+1, but there'
Hi Scott,
Nice work! In the mean time, we need to add the code:
XMEM=0
while read TYPE VALUE UNITS; do
case ${TYPE} in
MemFree:|SwapFree:)
XMEM=$((${XMEM} + ${VALUE}))
;;
esac
done < /proc/meminfo
XMEM=$((${XMEM} * ${XRAMPERC:-90} / 100))
echo " X server limited to ${
Ondrej Valousek wrote:
> I do not understand why is this code not available in ltsp-5. It was
> very useful thing!
Because we forgot, or no one had time, to add it in.
> Increasing the swap is not a solution - bring the code I mentioned back!
https://code.launchpad.net/~sbalneav/ltsp/scotts-gut
The problem is in FF consuming all available memory on the client for
pixmaps.
In LTSP 4.2 X startup scripts there was a code that limited the X server
memory to what was actually accessible by the thin client. This code
made the X server stable because otherwise once the FF consumes all
available
On Thu, 6 Sep 2007 15:19:27 +0300, Nadav Kavalerchik wrote
> Hi :-)
>
> we use firefox 2.0.0.6 on terminal's that have Intel i810 graphic display
> cards. we experience frequent crashes of X when browsing the net, on random
> sites.
>
> using opera / konqueror we never have problems,
> but we m
That distro are you using? I've been having this lately with dapper's
firefox. I think it has something to do with tabbed browsing, but I
can't figure out what yet.
Nadav Kavalerchik wrote:
>Hi :-)
>
>we use firefox 2.0.0.6 on terminal's that have Intel i810 graphic display
>cards.
>we exper
I "solved" (delayed) the problem by using ltspswapd and a 128M swap file.
Michael
Nadav Kavalerchik wrote:
> Hi :-)
>
> we use firefox 2.0.0.6 on terminal's that have Intel i810 graphic display
> cards.
> we experience frequent crashes of X when browsing the net, on random sites.
>
> using oper
Hi :-)
we use firefox 2.0.0.6 on terminal's that have Intel i810 graphic display cards.
we experience frequent crashes of X when browsing the net, on random sites.
using opera / konqueror we never have problems,
but we miss some of the features firefox has :-(
i remember some threads about this
24 matches
Mail list logo
