Seg fault caused by calling Visqol::VisqolApi::Measure about visqol HOT 4 CLOSED

Thanks for sharing this issue. I believe ViSQOL should work for multiple threads. There is a lightweight test for this. However, I think it requires multiple instances of the VisqolManager or VisqolAPI classes. Can you clarify if you were reusing the same instance across multiple threads?

from visqol.

thanks for responding.

Yes, we use multiple instances of VisqolApi. Each thread creates a new Visqol::VIsqolApi instance for each measurement.
The issue is intermittent. In some cases, the application runs for more than 15 mins before crashing

from visqol.

I see. As far as I'm aware there is no global or singleton in visqol code itself, but possibly one of the libraries/dependencies have this. How many threads are you running? Is it possible that the crash is due to memory exhaustion? The dynamic warping/alignment steps are quite memory intensive.

from visqol.

I think that issue is related to the audio files being compared. In case data in wav file is incomplete, or header file is written wrongly such an issue may appear. At least reproduced only when some files were written wrongly.

I'm closing this issue, but we have to be aware if we will try to compare some unchecked or wrong audio files - visqol may produce a crash with Segmentation Fault.

Thanks @mchinen for your interaction.

from visqol.