The madvice() busy loop will occur on all systems where page size is
bigger than 4KB. From supported architectures, e.g. MIPS and SPARC suffer
because of this.
See e.g. http://lists.debian.org/debian-mips/2012/07/msg00043.html
iceweasel is unusable on these platforms. :-(
--
To UNSUBSCRIBE, em
On Fri, Apr 27, 2012 at 08:12:51AM +0200, Mike Hommey wrote:
> Let me guess... alpha has non-4K page size.
Page size was 8K the last time I checked, which was admittedly a long
time ago. --Bob
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubs
On Thu, Apr 26, 2012 at 08:58:24PM -0500, Bob Tracy wrote:
> Earlier messages in this bug-report thread indicated use of Flash would
> also trigger the madvise() madness. I'm "happy" (?) to report that
> visiting Flash-enabled web sites reliably triggers this condition on the
> Alpha platform for
Earlier messages in this bug-report thread indicated use of Flash would
also trigger the madvise() madness. I'm "happy" (?) to report that
visiting Flash-enabled web sites reliably triggers this condition on the
Alpha platform for *all* releases of firefox/iceweasel after 9.0.1.
Michael Cree gets
Mike Hommey wrote:
> On Sat, Feb 25, 2012 at 09:14:07AM +, Jamie Heilman wrote:
> > So yeah, not checking errno and repeatedly attempting to MADV_DONTNEED
> > a range of memory that fails with a reason that isn't EAGAIN ... won't
> > wash. While the whole alsa/jack plugin thing is somewhat unu
On Sat, Feb 25, 2012 at 09:14:07AM +, Jamie Heilman wrote:
> Mike Hommey wrote:
> > > Jamie Heilman wrote:
> > > > #0 0x77407407 in madvise () from
> > > > /lib/x86_64-linux-gnu/libc.so.6
> > > > #1 0x7663169e in ?? () from /usr/lib/xulrunner-10.0/libmozjs.so
> > > > #2 0x00
Mike Hommey wrote:
> > Jamie Heilman wrote:
> > > #0 0x77407407 in madvise () from /lib/x86_64-linux-gnu/libc.so.6
> > > #1 0x7663169e in ?? () from /usr/lib/xulrunner-10.0/libmozjs.so
> > > #2 0x76628886 in ?? () from /usr/lib/xulrunner-10.0/libmozjs.so
> > > #3 0x7
On Sat, Feb 25, 2012 at 01:07:11AM +, Jamie Heilman wrote:
> Jamie Heilman wrote:
> > I've found this is really easy to reproduce if I use the native webm
> > player to playback video, but harder to produce (though it still
> > happens) if I use Flashplayer. What typically happens is that
> >
Jamie Heilman wrote:
> I've found this is really easy to reproduce if I use the native webm
> player to playback video, but harder to produce (though it still
> happens) if I use Flashplayer. What typically happens is that
> iceweasel stops responding and consumes a core's worth of CPU. An
> stra
Package: iceweasel
Version: 10.0.2-1
With the update to 10 I've been plagued by browser lockups and rabid
CPU consumption. I've narrowed down how to reproduce it ... it
requires a bit of setup though. First off, this is related to the way
in which JACK clients lock their memory, and the use of t
10 matches
Mail list logo
