Version: 2.16.1

What were you doing when the application crashed?
what I was doing when it crashed: scrolling the picture down by using down curser of my keyboard. 
but i think its more important what i did before: I opened the picture, checked it in full resolution by usig the "1" key, than back in full view "F11", and then to my surprise the picture was "fit to screen-sized" (normally it should be 100% resolution, but full sreen, i guess)  then going back from "full screen mode" by using "F11" it was again in full resolution (but of course not "fit to screen") then scrolling caused the viewer to crash. maybe its important to know, that I always have "image data" and "image taking conditions" opened (open = expanded) 


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 110833664 vsize: 0 resident: 110833664 share: 0 rss: 53604352 rss_rlim: 0
CPU usage: start_time: 1170098994 rtime: 0 utime: 451 stime: 0 cutime:436 cstime: 0 timeout: 15 it_real_value: 0 frequency: 2

Backtrace was generated from '/usr/bin/eog'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226422080 (LWP 8717)]
[New Thread -1298945120 (LWP 8720)]
[New Thread -1227928672 (LWP 8718)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 106361