I've noticed that if I keep Quest running for a long period of time, while I do a lot of code modifications, code creation, or codebase refactoring, with starting and stopping the game quite a few times, that the program starts to get very sluggish, takes a long time to load code in the interface and eventually crashes to desktop. And when you load it back up, it runs smoothly again and everything loads super fast.

Generally that is indicative of a memory leak aka, the program not properly deleting its pointers when it no longer needs them, and the pointers eventually eat up all the memory available. I mention it as I noticed that Quest got an update a few months back and thought I'd mention it in case the developers of quest didn't know there was a memory leak.

open task manager and watch the memory use to be sure...
I know Face Book, and FB games seem to like to use more and more memory until they get closed.
I haven't noticed it with Quest.
(yet)