Open olafth opened 2 months ago
I found the problem. It happens when the recognizer is not disposed of correctly. This should definitely raise an exception, but a SIGSEGV is a bit much :)
Have you solved your problem?
Yes. In my comment on April 25th I mentioned the resolution. It happens when the vosk recognizer is not disposed of correctly. If you use it in a try-with-resources block like
try (InputStream inputStream = is; Recognizer recognizer = rec) {...}
the problem does not occur.
I have a RSocket channel, send data and recognition works. On resource cleanup, specifically on recognizer.close a SIGSEGV happens. I am using VoskApi 0.3.45 and also compiled the current master (0.3.48) and installed libvosk.so in /usr/lib. No changes. OS is Kubuntu 22.04. The SIGSEGV happens both with a self written RSocket client and rsc.jar and the commandline
java -jar rsc.jar --debug --channel --load ./de_1.wav --route audio.bytes.de tcp://localhost:7000