Simple Scan Crash - "failed to allocate" in debug output

Bug #1138236 reported by Rik Shaw
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Simple Scan
Incomplete
Undecided
Unassigned

Bug Description

Seemingly random crashes, here is the hardware info:

Simple Scan version 3.4.1
OS: Ubuntu 12.04 64 bit (actually Mint 13 Cinnamon so apport doesn't work for me I don't think)
Kernel: 3.2.0-38
lsusb for Scanner: Bus 002 Device 009: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110

Crashes (simple scan closes down) happen often when clicking "scan" to scan an additional page (multipage scans). Sometimes after 10+ scans, sometimes after only 1 or 2 scans. Sometimes the scanner has to be "unplugged - replugged" to get it back or else just restarting simple-scan indicates "scanner not detected". But that last part is only "sometimes".

Running "simple-scan" from the terminal gives the following output when the crash occurs:

(simple-scan:6094): GLib-GObject-CRITICAL **: g_signal_emit_by_name: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(simple-scan:6094): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer

(this is repeated many times..... more times than my terminal output history retains!)

Then, I tried "simple-scan -d" from the terminal (for debug info), and got this info on a crash:

(simple-scan:6332): GLib-ERROR **: /build/buildd/glib2.0-2.32.3/./glib/gmem.c:165: failed to allocate 303511022320 bytes
Trace/breakpoint trap

This last info seems likely the most relevant, with the "allocate" message I am wondering if it is a memory allocation problem? I see other possible bugs like this but don't know if they are the same or not.

I am willing to try different versions, different kernels, xsane, etc., but would appreciate advice on what to try in what order.

Simple Scan is a great program but these nagging crashes have users confused and insecure!

Rik Shaw (rik-shaw)
summary: - Canoscan LIDE 110 Crash - Memory Issue?
+ Simple Scan Crash - "failed to allocate" in debug output
Revision history for this message
Rik Shaw (rik-shaw) wrote :

Update: I have installed xsane and tried some similar scanning processes and CANNOT get it to crash. So this is not "definitive" but it does appear that the issue is isolated to simple-scan.

Revision history for this message
Michael Nagel (nailor) wrote :

can you try with the current development version:

https://github.com/mnagel/simple-scan/blob/master/README.md

Revision history for this message
Fredrik Nyqvist (fredrik-nyqvist) wrote :
Download full text (4.8 KiB)

I also have the problem where simple-scan craches after clicking on "scan" button. Sometimes it crahes in the middle of a scanning process.

I am running Debian 7.2
simple-scan: 3.4.2

Here is a report about similar problem on Debians bugtracker: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680601

Here is some output I get when running simple-scan with gdb:

 -> gdb simple-scan
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/simple-scan...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/simple-scan
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeff00700 (LWP 7201)]
[New Thread 0x7fffeebd4700 (LWP 7202)]
[New Thread 0x7fffed25f700 (LWP 7203)]
[New Thread 0x7fffd77b7700 (LWP 7204)]
WARNING: gnome-keyring:: couldn't connect to: /home/fredrik/.cache/keyring-Sz0LZe/pkcs11: Filen eller katalogen finns inte
[Thread 0x7fffed25f700 (LWP 7203) exited]
[Thread 0x7fffd77b7700 (LWP 7204) exited]
[Thread 0x7fffeff00700 (LWP 7201) exited]
[Thread 0x7ffff7fd2920 (LWP 7198) exited]
[Inferior 1 (process 7198) exited normally]
(gdb) run
Starting program: /usr/bin/simple-scan
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeff00700 (LWP 7206)]
[New Thread 0x7fffeebd4700 (LWP 7207)]
[New Thread 0x7fffed274700 (LWP 7208)]
[New Thread 0x7fffd3779700 (LWP 7209)]
WARNING: gnome-keyring:: couldn't connect to: /home/fredrik/.cache/keyring-Sz0LZe/pkcs11: Filen eller katalogen finns inte
[Thread 0x7fffed274700 (LWP 7208) exited]
[Thread 0x7fffd3779700 (LWP 7209) exited]
[Thread 0x7fffeebd4700 (LWP 7207) exited]
[Thread 0x7ffff7fd2920 (LWP 7205) exited]
[Inferior 1 (process 7205) exited normally]
(gdb) run
Starting program: /usr/bin/simple-scan
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeff00700 (LWP 7268)]
[New Thread 0x7fffeebd4700 (LWP 7269)]
[New Thread 0x7fffed25f700 (LWP 7270)]
[New Thread 0x7fffd377c700 (LWP 7271)]
WARNING: gnome-keyring:: couldn't connect to: /home/fredrik/.cache/keyring-Sz0LZe/pkcs11: Filen eller katalogen finns inte
[New Thread 0x7fffcff7d700 (LWP 7273)]
[Thread 0x7fffcff7d700 (LWP 7273) exited]

** (simple-scan:7267): WARNING **: scanner.vala:977: Unable to disable compression, please file a bug
[New Thread 0x7fffcff7d700 (LWP 7274)]
[Thread 0x7fffcff7d700 (LWP 7274) exited]
[New Thread 0x7fffcff7d700 (LWP 7275)]
[Thread 0x7fffcff7d700 (LWP 7275) exited]
[New Thread 0x7fffcf77c700 (LWP 7276)]
[Thread 0x7fffcf77c700 (LWP 7276) exited]

(simple-scan:7267): GLib-GObject-WARNING **: instance of invalid ...

Read more...

Revision history for this message
Michael Nagel (nailor) wrote :

Fredrik, lets keep these reports separate. They might or might not be related, and it is easier to merge later than to untangle.

Changed in simple-scan:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.