José Valim 8f25c25c7a Trigger the GC after evaluation and intellisense (#807) ... This reduces memory consumption by the runtime, especially when using intellisense features which may generate a lot of garbage. There is an odd chance this can generate slow downs in certain cases but, for that to happen, I would expect the notebook to either have a lot of data allocated or many users interacting with it and triggering completion and other features at the same time. We don't worry about the second case because the goal is to move completion to an ephemeral separate process anyway, which would remove the need for GC during completion altogether (and allow several completions to run concurrently). If this happens, we can consider moving GC out of the evaluator and have the session explicitly trigger it once it terminates a chain of evaluation. It is also worth triggering the GC whenever we forget an evaluation context.		2021-12-15 12:25:09 +01:00
..
livebook	Trigger the GC after evaluation and intellisense (#807)	2021-12-15 12:25:09 +01:00
livebook_cli	Revert to URI.new! (#784)	2021-12-09 20:46:45 +01:00
livebook_web	Added margin on copy button (#796)	2021-12-12 20:26:10 +01:00
livebook.ex	Automatically back up notebooks without a file (#736)	2021-12-04 16:29:14 +01:00
livebook_cli.ex	Include full stacktrace for unexpected exceptions (#781)	2021-12-09 15:44:23 +01:00
livebook_web.ex	Refactor modals with JS commands (#669)	2021-11-02 22:34:44 +01:00