zlib segmentation fault in default package
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| zlib (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: zlib1g
If I press PrintScreen on my keyboard a number of times (sometimes it takes 20, other times it's 5, but varies) gnome-screenshot semi-regularly generates a bug report as follows:
Memory status: size: 63733760 vsize: 0 resident: 63733760 share: 0 rss: 17010688 rss_rlim: 0
CPU usage: start_time: 1171574803 rtime: 0 utime: 70 stime: 0 cutime:70 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/
(no debugging symbols found)
Using host libthread_db library "/lib/tls/
(no debugging symbols found)
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225701712 (LWP 10190)]
(no debugging symbols found)
...
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb73ed34b in __waitpid_nocancel ()
from /lib/tls/
#2 0xb7eaa1b6 in gnome_gtk_
#3 <signal handler called>
#4 0xb731b37c in memcpy () from /lib/tls/
#5 0xb71e0e8d in deflateCopy () from /usr/lib/libz.so.1
#6 0xb71e1a44 in deflateInit_ () from /usr/lib/libz.so.1
#7 0xb71e1f10 in deflate () from /usr/lib/libz.so.1
#8 0xb709c101 in png_write_chunk () from /usr/lib/
#9 0xb709c64b in png_write_chunk () from /usr/lib/
#10 0xb70a0774 in png_write_row () from /usr/lib/
#11 0xb70a0937 in png_write_rows () from /usr/lib/
#12 0xb6db0a79 in fill_info ()
from /usr/lib/
#13 0x0825a2f8 in ?? ()
#14 0xbfa3e370 in ?? ()
#15 0x00000001 in ?? ()
#16 0x00000400 in ?? ()
#17 0x00000008 in ?? ()
#18 0x00000006 in ?? ()
#19 0x00000000 in ?? ()
Thread 1 (Thread -1225701712 (LWP 10190)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb73ed34b in __waitpid_nocancel ()
from /lib/tls/
No symbol table info available.
#2 0xb7eaa1b6 in gnome_gtk_
No symbol table info available.
#3 <signal handler called>
No symbol table info available.
#4 0xb731b37c in memcpy () from /lib/tls/
No symbol table info available.
#5 0xb71e0e8d in deflateCopy () from /usr/lib/libz.so.1
No symbol table info available.
#6 0xb71e1a44 in deflateInit_ () from /usr/lib/libz.so.1
No symbol table info available.
#7 0xb71e1f10 in deflate () from /usr/lib/libz.so.1
No symbol table info available.
#8 0xb709c101 in png_write_chunk () from /usr/lib/
No symbol table info available.
#9 0xb709c64b in png_write_chunk () from /usr/lib/
No symbol table info available.
#10 0xb70a0774 in png_write_row () from /usr/lib/
No symbol table info available.
#11 0xb70a0937 in png_write_rows () from /usr/lib/
No symbol table info available.
#12 0xb6db0a79 in fill_info ()
from /usr/lib/
...
I also regularly use the flam3 rendering engine (www.flam3.com), which can write out images in PNG format. When compiled against zlib 1.2.3-13ubuntu2 and libpng1.
This bug is occurring on an ASUS M2N-SLI Deluxe motherboard and an AMD Athlon X2 4600+ processor, running 32-bit Edgy. I am not overclocking the system at all, and I've run both Memtest86+ and some of the Prime95 tests to ensure that components are in working order. I'll be happy to provide any additional information as necessary - just ask.
| description: | updated |
| description: | updated |
| Mark Brown (broonie) wrote | #1 |
| Spotworks LLC (spotworks) wrote | #2 |
It is very unlikely that this is a problem in either libpng or zlib. If there were such a serious problem with either then I would expect that very many more users would be reporting it. In the case of zlib there is no CPU or motherboard specific code in there - exactly the same code runs on all systems of a given architecture and it is all pure memory operations.
If, as you believe, the problem is motherboard or hardware specific then it is much more likely that any software problem is in the kernel.