Simple Scan Crash - "failed to allocate" in debug output
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-
(simple-scan:6094): GLib-GObject-
(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/
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!
summary: |
- Canoscan LIDE 110 Crash - Memory Issue? + Simple Scan Crash - "failed to allocate" in debug output |
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.