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
Simply opening a couple of Asciidoctor files in 2.5 of the editor lets the memory consumption of the ASP server quickly raise to multiple GB quickly. I've opened 10 documents, added a minor change and saved them. The Java process grew to 3.67 GB and doesn't shrink back if the files are closed.
I would appreciate it if the server was shut down after the last Asciidoctor document was closed so that the memory is not unnecessarily consumed.
Switching to a locally installed Asciidoctor (via the preferences) of course solves that issue.
The text was updated successfully, but these errors were encountered:
Simply opening a couple of Asciidoctor files in 2.5 of the editor lets the memory consumption of the ASP server quickly raise to multiple GB quickly. I've opened 10 documents, added a minor change and saved them. The Java process grew to 3.67 GB and doesn't shrink back if the files are closed.
I would appreciate it if the server was shut down after the last Asciidoctor document was closed so that the memory is not unnecessarily consumed.
Switching to a locally installed Asciidoctor (via the preferences) of course solves that issue.
The text was updated successfully, but these errors were encountered: