Description of problem:
I am currently testing a new scanner. Testing in 2400dpi works fine, 4800dpi, it crashes.

I think that, this might be related to SANE using /tmp/. If /tmp fills up it crashes, I could be wrong though.
But this appears to ahppen in 4800dpi mode only, and files are left behind in /tmp.

I wonder, if xsane should have its own /tmp dir under /var ?!?!?! And also on restart clean up the /tmp dir of its own files ?

Version-Release number of selected component:
xsane-0.999-28.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        xsane
crash_function: __memmove_sse2_unaligned_erms
executable:     /usr/bin/xsane
journald_cursor: s=c9f13ae252be4bc2879f3d7f516ceca4;i=b0097;b=d34996738b3340958bd2849242d7ac89;m=122a43d4a;t=56f9d596baa61;x=c7c2092df8817586
kernel:         4.17.2-200.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __memmove_sse2_unaligned_erms at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:455
 #1 xsane_viewer_read_image at ../../src/xsane-viewer.c:2547
 #2 xsane_viewer_new at ../../src/xsane-viewer.c:3121
 #3 xsane_scan_done at ../../src/xsane-scan.c:1226
 #4 xsane_read_image_data at ../../src/xsane-scan.c:551
 #5 xsane_start_scan at ../../src/xsane-scan.c:1869
 #6 xsane_scan_dialog at ../../src/xsane-scan.c:2169
 #11 gtk_real_button_released at gtkbutton.c:1712
 #16 gtk_button_button_release at gtkbutton.c:1604
 #17 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:84