Home › Forums › OpenEars plugins › RapidEars startRealtimeListeningWithLanguageModelAtPath memory leaks › Reply To: RapidEars startRealtimeListeningWithLanguageModelAtPath memory leaks
“Creating shared instance of OEPocketsphinxController” is the second line. But I really don’t think those logs are from a project successfully linked with a current version of RapidEarsDemo.framework. If the Rejecto 2.5 and OpenEars 2.5 logging work as expected, and all three of them work as expected when I run it locally, and the local behavior when stopping listening is different on your setup, I think the logging problem is most likely somehow connected with linking to an old copy of RapidEars locally.
I believe that it is possible that there is an extraordinary bug of some kind which causes the symptoms of just the RapidEars framework not logging just some of its logging output, so I am not ruling that out, but it seems like a lower probability than linking to an old framework right now. There is some RapidEars logging appearing (“Starting listening”), so the issue isn’t that there is no logging output from RapidEars at all, but that the new logging output that was added to RapidEars 2.5 is not apparent.