Stability and Memory Pressure in 8.2

[S Page]

Tomeu Vizoso wrote:

> Read has serious memory problems because renders whole pages
> into memory, regardless of what is the viewed area. Any chance the
> first pages of the PDF you opened contained big images?

Nope, it's a saved Project Gutenberg PDF 
Coradella_Collegiate_Bookshelf_Collection_austen-persuasion.pdf, looks 
like it has one small image.
Of course when I reproduce everything works fine.

Is there *anything* testers can run before or after their XO goes funny? 
  My fantasy would be a section in 
http://wiki.laptop.org/go/Friends_in_testing :

   "Run log_mem.py from a console as you start Sugar.  This snapshots 
memory every 10 seconds to a rotating set of files in tmpfs until it 
detects that the machine has serious memory problems, then it runs a 
detailed /sys/procmem dump.  It also runs strace on the OOMKiller 
thread.  If your XO locks up, zip this directory and attach it to bug 4321."

Without something like that, it'll be hard to get anything more from 
testers than anecdotes.

Sincerely,
--
=S