Viewer handler keeps reference to Navigator
See original GitHub issueMy project has 2 active navigators. One is regular navigator that shows everything. The other is navigator for the current image that user is viewing.
My project has custom logic that detect when user is viewing an image at a particular zoom level and creates a navigator for it by
viewer.slidesNavigator = new OpenSeadragon.Navigator(options);
By taking memory snapshots, we found that handlers in the main viewer keeps a reference navigators that are no longer in use.
Thus the navigator will never be garbage collected
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Cannot update a component (`StackNavigator`) while ... - GitHub
I just discovered my issue is occuring when I use navigation.setParams() outside of useEffect(). Found a refrence here. setParams/setOptions etc ...
Read more >Unable to resolve module 'react-navigation' - Stack Overflow
This error means that either you haven't installed the react-navigation module or that you have installed the module but didn't re-built ...
Read more >React Native Navigation: Tutorial with examples
In this React Native Navigation tutorial, we'll show you some examples of navigation patterns you can implement with React Navigation.
Read more >Class: Viewer - OpenSeadragon
Enables and displays the reference strip based on the currently set tileSources. Works only when the Viewer has sequenceMode set to true. Source:....
Read more >Interact programmatically with the Navigation component
Create a NavHostFragment · Reference a destination using NavBackStackEntry · Share UI-related data between destinations with ViewModel · Modifying ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I believe this is now fixed by #1832.
@JoFrMueller Wonderful… thank you for jumping on this!