https://bugs.kde.org/show_bug.cgi?id=395391
--- Comment #2 from Bob Mahar <[email protected]> --- Same issue with xsane ( latest ) but different failure mode. With xsane, I observe it building a pixmap temp file which corresponds to the size of the scan. The scan completes. Once the scan completes, the xsane UI segfaults and disappears. However the pixmap file is left behind. This file is a consistent PNM formatted file and can be opened by GIMP 2.10 - it is a bunch of static, however I think this is because of the packing of the 48-bit samples. ( You can see hints of structure and outlines and so on. ) So I am pretty sure the sane driver layer is acquiring a scan from the scanner and presenting this to the application. However, again, if the temp file > 2GB, the xsane UI explodes. The difference in behaviour is that xsane seems to acquire the whole image before crashing, whereas skanlite seems to be looking at the data as it is being scanned. But yeah, similar outcomes, different failure modes. -- You are receiving this mail because: You are watching all bug changes.
