fix: memory leaks in DefaultViewManager #1414
Open
+15
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses memory leaks caused by
windowevent listeners not being removed properly when destroying a book or rendition.Changes include
Why this matters
Detached DefaultViewManager, Rendition, and Book were found to persist in memory after book.destroy() due to unremoved event listeners.
This fix ensures event listeners are correctly released, preventing unnecessary memory usage during repeated book loads/unloads.
Issue Reproduction
Run the snippet above in a web browser. Click the "Open EPUB" button to load an EPUB file, and then click "Close EPUB" to unload it.
Next, open the browser DevTools console and run:
getEventListeners(window);.You will notice that there are two event listeners remain attached:
unloadandorientationchange.If you switch to the Memory tab and take a heap snapshot, you’ll see that the Book and Rendition instances are still retained in memory.