[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Slowdowns & lockups in Firefox/Minefield.
- To: Steve Baker <email@example.com>
- Subject: Re: [Public WebGL] Slowdowns & lockups in Firefox/Minefield.
- From: Ilmari Heikkinen <firstname.lastname@example.org>
- Date: Fri, 4 Jun 2010 23:28:54 +0300
- Cc: public webgl <email@example.com>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:cc; bh=fkcGNON6fzIqtNWbaEbpwa1ogdyUfgRNLLFdP2tihho=; b=DKHvMhPkmJezvdCQtUok3Y0Y/EDoML4Ff3sFhBowBsdGTqu4ORc7QiaYbF0UalvGOw jynZ40cfRCzmmO0Hbi9MZq17q9kOOtrV+pK3/url9yq9pe8HE5oi3awyunWiP0mzbLkQ TsqlvR7npat4FrJBAj9yDsBfHGHMNGP8REqNw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc; b=gPX9UWO6/JyrNMGJB0e+Z8L+xXh6ace5wh1qDb4yoWzOISTvh5eiTFXe4uckZTYVz5 jpmTU3fHdeKs30qRB+N3F9aD1ULk8uZIcS+J07LkJMJtnmtlTFW0HTXTlXkOSY7lIM+0 Bnv71EKbpb9dJxDBUJof9B9x95upuVEzVNtDc=
- In-reply-to: <4C088A2D.firstname.lastname@example.org>
- References: <4C088A2D.email@example.com>
- Sender: firstname.lastname@example.org
Steve Baker <email@example.com> kirjoitti 4.6.2010 kello 8.07:
Forgive me if you guys already know this - but my (increasingly hefty)
application seems to only run a half dozen times (assuming I keep
hitting 'Reload') before Firefox's frame rate slows down dramatically
(like one frame every two seconds) - or perhaps locks up
kinda feels like maybe some resources are not being free'd up...but
that's just a guess. Killing and restarting the browser reliably
This is with: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:
I presume we don't expect the application to do any specific
cleanup...I'm not currently doing anything like that.
Firefox was at one point doing GL context destruction at garbage
collection time (instead of document unload). If it's still doing
that, the context and the resources allocated by it are only freed
after doing some thirty megabytes of JS allocation. In that case, if
you have a large canvas and don't allocate much, you might run out of
GPU resources before triggering GC. But I don't know too well how the
latest builds do things, so I might well be wrong.
You are currently subscribed to firstname.lastname@example.org.
To unsubscribe, send an email to email@example.com with
the following command in the body of your email: