Closed jbmorley closed 2 years ago
I've checked through func recognize(path:)
and func getFileInfo(path:)
and they look fine in terms of error handling. I'm more inclined to think this might be a threading issue where this OpoInterpreter
instance is being used by multiple threads concurrently?
I don't believe we're sharing the interpreter between threads anymore but I'll keep an eye open for that.
I don't think I've ever seen this on device. Perhaps it's some weird simulator bug? I would feel deeply uncomfortable with that explanation, but the lack of on-device repro is nudging me towards pushing it out into Future.
Pushing this into Future; we can bring it back if we get a repro.
Closing as invalid. I've not seen this issues on target. We can always re-open or raise a new issue if we see this again.
Perhaps something in our Lua code is failing to handle an error?