look at memory usage
Closed this issue · 2 comments
chriseidhof commented
This seems to have to do with highlighting... and only happens on Linux.
chriseidhof commented
This could actually have to do with SourceKitten, I saw some other things there as well. Two possible ways to deal with it:
Rather than highlighting all the snippets individually, we could concatenate them (maybe per episode?), highlight that, and then pull the highlighted code apart again.
Or we could use sourcekitten on the command line. That will be slower, but at least it'll give back its memory once the process is done.
chriseidhof commented
This could be helpful in diagnosing the problem:
https://developer.ibm.com/swift/2018/01/26/diagnosing-server-side-swift-memory-leaks/