You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quill appears to be leaking memory in general. In my current use case I have an application that creates and removes many instances of Quill on a single page. Doing some memory leak analysis it appears that many of the event emitters used between the quill editor and the keyboard/scroll/modules systems result in memory leaks.
Steps for Reproduction
While a bit of a crude reproduction I was able to use the playground to reproduce a form of this memory leak.
Enter the following into JS section of the playground
varlastId=0;setInterval(()=>{// Proxy metric to show growth only works in chromeconsole.log(performance.memory)},5000)document.getElementById('add-editor').onclick=()=>{varel=document.createElement('div');varid=`editor-container-${lastId++}`;el.id=id;varexistingArea=document.getElementById('editor-area');existingArea.append(el);varlargeValue=newArray(999999);largeValue.fill(9);newQuill('#'+id,{modules: {toolbar: null},placeholder: 'Compose an epic...',theme: 'snow',// or 'bubble',foo: largeValue});}document.getElementById('remove-editor').onclick=()=>{vartargetEditor=`editor-container-${--lastId}`;document.getElementById(targetEditor).remove();}
Enter the following into the html section of the playground
Quill 2.0 has been released (announcement post) with many changes and fixes. If this is still an issue please create a new issue after reviewing our updated Contributing guide 🙏
Quill appears to be leaking memory in general. In my current use case I have an application that creates and removes many instances of Quill on a single page. Doing some memory leak analysis it appears that many of the event emitters used between the quill editor and the keyboard/scroll/modules systems result in memory leaks.
Steps for Reproduction
While a bit of a crude reproduction I was able to use the playground to reproduce a form of this memory leak.
Expected behavior:
Memory should eventually go down and stay down
Actual behavior:
Memory keeps climbing higher and higher with each new set of added/removed editors
Platforms:
MacOS Monterey 12.5.1 Chrome 109.0.5414.87 (but I suspect this applies to many other versions)
Version:
1.3.7
The text was updated successfully, but these errors were encountered: