Your message dated Thu, 22 May 2008 19:50:50 -0400
with message-id <[email protected]>
has caused the report #482336,
regarding keyjnote: crashes while displaying a PDF file which renders fine in
to be marked as having been forwarded to the upstream software
author(s) [email protected]
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Re: Bug#482336: keyjnote: crashes while displaying a PDF file which renders fine in Xpdf
Thu, 22 May 2008 19:50:50 -0400
Here is a fresh bug report (for initial report please see
I thought that it is caused by insufficient VRAM... swap space is quite
large... so shouldn't be... in any case -- please see below and the url
Thanks in advance for resolving it
On Fri, 23 May 2008, Francesco Poli wrote:
> On Wed, 21 May 2008 19:34:50 -0400 Yaroslav Halchenko wrote:
> > didn't reproduce the bug -- went through ok - didn't stall at any
> > slide... didn't crash after...
> > lets first verify that your /tmp/ had sufficient amount of space ;)
> $ df --si /tmp/
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/...-tmp 390M 11M 360M 3% /tmp
> > and then your RAM (and virtual memory)
> $ free -b
> total used free shared buffers cached
> Mem: 507858944 501751808 6107136 0 13824000 209612800
> -/+ buffers/cache: 278315008 229543936
> Swap: 2000674816 0 2000674816
> > -- total amount of VRAM needed for
> > caching your presentation is around 460MB. not sure what was max size of
> > rendered page -- but I guess it would be great if your /tmp had at least
> > 100MB free?
> I can understand that the presentation is long and so it may be not
> possible to cache it entirely, depending on the available resources...
> But anyway, we are talking about an unhandled exception here. A robust
> program should be able to cope with exceptions without crashing.
> I think keyjnote should check (by catching relevant exceptions) whether
> a required resource (mass memory, central/virtual memory, ...) could be
> successfully acquired. In case it could not, keyjnote should refrain
> from caching the entire presentation and cache only a (moving) part of
> it... without crashing!
> I hope I clarified what I mean.
> Please forward this bug report to upstream, if appropriate.
Research Assistant, Psychology Department, Rutgers-Newark
Student Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
--- End Message ---