Comment 33 for bug 843361
Revision history for this message
| Michael Nagel (nailor) wrote Re: simple-scan crashed with SIGSEGV in g_closure_invoke() | #33 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Thank you very much. From my point of view this sounds as if there is a small but crucial difference between:
A:
- close simple scan
- start simple scan
B:
- click "new document" in simple scan
these should be functionally equivalent (with some potential optimization in approach B).
in reality they are not, and that is the problem.
where could it fail:
- internal state of the scanner could be invalid after running the commands from approach B
- state of simple scan could be invalid after running the commands from approach B, this could especially affect buffers (freed them and kept dangling pointers, ...)
I will ask Robert to double check this.