Crash due to undefined path about allusion HOT 3 CLOSED

Additionally, the Inspector and FileInfo seem relevant as I keep errors from React. Something doesn't get cleaned up.

Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.
in wrappedComponent (created by FileInfo)
in FileInfo (created by Inspector)

Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
in InlineSVG
in Blueprint3.Icon (created by Blueprint3.Button)
in button (created by Blueprint3.Button)
in Blueprint3.Button (created by MultiTagSelector)
in div (created by Blueprint3.TagInput)
in Blueprint3.TagInput (created by Blueprint3.QueryList)
in div (created by Blueprint3.QueryList)
in span (created by InnerReference)
in Blueprint3.ResizeSensor (created by InnerReference)
in InnerReference (created by Context.Consumer)
in Reference (created by Blueprint3.Popover)
in span (created by Blueprint3.Popover)
in Manager (created by Blueprint3.Popover)
in Blueprint3.Popover (created by Blueprint3.QueryList)
in Blueprint3.QueryList (created by Blueprint3.MultiSelect)
in Blueprint3.MultiSelect (created by MultiTagSelector)
in MultiTagSelector (created by wrappedComponent)
in wrappedComponent (created by FileTag)

from allusion.

I haven't come across these errors yet... That first one is weird, do you know whether it occurs for a specific file or just randomly?
That second one seems to originate from the react-inlinesvg package. There's no issue about this there yet, but there are some related changes incoming in the next release: gilbarbara/react-inlinesvg#106

from allusion.

It happens when you change the view and somehow in between the selection of the files must get messed up randomly. It doesn't seem to be related with the files. You actually saw the errors whenever the app crashed when someone was presenting something.
My guess is that in one of the useEffect calls, something doesn't get cleaned up or even in a mobx useObserver hook since the errors come from components that are wrapped in an observer. The issue is due to some state changes not being propagated properly. I hope it is something we can resolve and nothing upstream.

from allusion.