Porcupine crash observed when multiple porcupine instances(handles) are used with multiple threads for keyword detection in multiple audio channels about porcupine

[arunnadesh]

Thanks for the response...I have already implemented the second solution... ☺️

[kenarsa]

Hi Arun,

The stack trace is quite helpful. Thanks. The problem is that the math module is shared between different instances of the objects and when the first one quits it also releases resources acquired by math module. We need to do some reference counting here or give each instance a different instance of math module. I will add this to our TODO list and will push it out for next release. But it will take us a while to get to it considering other priorities.

In the meantime. I can think of a couple of things you can do to not get blocked:

1- Make a copy of .so for each thread (not nice) but works for sure.
2- Have a pool of Porcupine instances that you never delete (like ThreadPool but PorcupinePool!). Then you can assign them to new threads when you spawn them.

Let me know what you think.

Thanks a lot for helping us make Porcupine a better library.

[kenarsa]

Hi Arun,

Could you please check and see if the issue is resolved in v1.3?

Thanks

[arunnadesh]

Thanks... I will check and update...

[kenarsa]

any updates?

[kenarsa]

closing due to inactivity. feel free to reopen if the issue is not resolved.