'scanimage -L' from 'graphics/sane-backends' causes system crashes after a while

[Yuri]

For my system this works with a 100% reliability: run 'scanimage -L' (or
just scan something), and system will crash after a few hours or so.

'-L' option calls the function 'sane_get_devices', which has about 90
implementations there. It calls all of them trying to find a scanner.
Some of them cause system to crash later.

My real scanner is on the wifi network. I'm not sure if the real scanner
is what causes the problem, or maybe it's some other test among these 90
'sane_get_devices' functions that causes this problem.

What is the easiest way to troubleshoot this? The problem is that the
crash doesn't come right away.

11.1-STABLE

Yuri

[Hans Petter Selasky]

Post by Yuri
For my system this works with a 100% reliability: run 'scanimage -L' (or
just scan something), and system will crash after a few hours or so.
'-L' option calls the function 'sane_get_devices', which has about 90
implementations there. It calls all of them trying to find a scanner.
Some of them cause system to crash later.
My real scanner is on the wifi network. I'm not sure if the real scanner
is what causes the problem, or maybe it's some other test among these 90
'sane_get_devices' functions that causes this problem.
What is the easiest way to troubleshoot this? The problem is that the
crash doesn't come right away.
11.1-STABLE

Try ktrac'ing the program first, or run from inside of gdb801 from ports:

gdb801

Post by Yuri
file scanimage
run -L

--HPS

[Alan Somers]

Please open an issue on bugzilla, and include the full stacktrace of the
crash.

Post by Yuri
For my system this works with a 100% reliability: run 'scanimage -L' (or
just scan something), and system will crash after a few hours or so.
'-L' option calls the function 'sane_get_devices', which has about 90
implementations there. It calls all of them trying to find a scanner. Some
of them cause system to crash later.
My real scanner is on the wifi network. I'm not sure if the real scanner
is what causes the problem, or maybe it's some other test among these 90
'sane_get_devices' functions that causes this problem.
What is the easiest way to troubleshoot this? The problem is that the
crash doesn't come right away.
11.1-STABLE
Yuri
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-hackers

[Yuri]

Post by Alan Somers
Please open an issue on bugzilla, and include the full stacktrace of the
crash.

It actually freezes, doesn't crash. So I won't be able to get a stack trace.


Yuri

[Hans Petter Selasky]

Post by Yuri

Post by Alan Somers
Please open an issue on bugzilla, and include the full stacktrace of the
crash.

It actually freezes, doesn't crash. So I won't be able to get a stack trace.

Hi,

"procstat -ak " might give some clues.

--HPS

[Yuri]

Post by Yuri
For my system this works with a 100% reliability: run 'scanimage -L'
(or just scan something), and system will crash after a few hours or so.
'-L' option calls the function 'sane_get_devices', which has about 90
implementations there. It calls all of them trying to find a scanner.
Some of them cause system to crash later.
My real scanner is on the wifi network. I'm not sure if the real
scanner is what causes the problem, or maybe it's some other test
among these 90 'sane_get_devices' functions that causes this problem.
What is the easiest way to troubleshoot this? The problem is that the
crash doesn't come right away.
11.1-STABLE

For the record: I never found the reason why this command crashes the
system.

But there is a workaround: in the file /usr/local/etc/sane.d/dll.conf
comment out all scanners except the one that you have. This prevents
sane from scanning all possible scanners, and avoids system crashes.


Yuri