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
Using this library causes severe performance issues, particularly in Chrome:
Chrome: The browser runs out of memory, with CPU usage spiking to nearly 100% as shown in Chrome DevTools. Additionally, an excessive number of DOM nodes are created, contributing to the problem.
Other Browsers: While the issue does not result in an out-of-memory error, it still leads to noticeable performance degradation.
Steps to Reproduce:
Set a fixed height on ngx-monaco-editor instance (e.g., 800px).
Populate the editor with a large amount of text.
Scroll up and down quickly (at a faster pace than typical reading).
Observe the performance impact:
Noticeable performance degradation, particularly in Chrome.
In Chrome, extreme memory usage and high CPU consumption can occur.
This issue becomes more evident when the text within the editor is large enough to stress the rendering and scrolling performance.
My app is breaking because of this. Makes me believe there monaco-editor demos are really small because of this...
This is causing out of memory issues: (see chrome debug)
The text was updated successfully, but these errors were encountered:
Using this library causes severe performance issues, particularly in Chrome:
Chrome: The browser runs out of memory, with CPU usage spiking to nearly 100% as shown in Chrome DevTools. Additionally, an excessive number of DOM nodes are created, contributing to the problem.
Other Browsers: While the issue does not result in an out-of-memory error, it still leads to noticeable performance degradation.
Steps to Reproduce:
This issue becomes more evident when the text within the editor is large enough to stress the rendering and scrolling performance.
My app is breaking because of this. Makes me believe there monaco-editor demos are really small because of this...
This is causing out of memory issues: (see chrome debug)
![image](https://private-user-images.githubusercontent.com/33399876/403444004-d02be2b5-a261-4cdb-ac12-6f58a71d3983.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4NjgzMTgsIm5iZiI6MTczODg2ODAxOCwicGF0aCI6Ii8zMzM5OTg3Ni80MDM0NDQwMDQtZDAyYmUyYjUtYTI2MS00Y2RiLWFjMTItNmY1OGE3MWQzOTgzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA2VDE4NTMzOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNjYzBlOWIyNWVlNmI4ZWUwNjUwNDQwNTBjMWZmYjBmNjNmNmMxNWNiNTgyNGNkMmI0NGNjMmIwOWZkNzIzNDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.1VL-q9NaoBVGir9rqHfOzeV0i9z18iZkTN2PpcyLYtM)
The text was updated successfully, but these errors were encountered: