danielcranford
danielcranford
Ahh, missed the fact `Arrays.compare(byte[], byte[])` was added in JDK 9. ByteByffer.compareTo() still works. `ByteBuffer.wrap(byte[]).compareTo(ByteBuffer.wrap(byte[])` works as an alternative to Arrays.compare though adds allocation cost to the compare
Your stack trace is from the primordial thread created by the OS for the java process. Ever since [Java 6](https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6316197), the primordial thread loads the VM, starts a thread to...
I have the same issue. Lapce is taking 3.9 GB for a project VS code only took 1.1 GB to open. No plugins installed. Yes it's a big project, but...
Proof: I reopened Lapce. It automatically opened the same project folder. I didn't open any files. Memory usage started going up steadily. Here are successive screenshots.  
Here's the logs folder. They seem unremarkable. [logs.zip](https://github.com/lapce/lapce/files/15069787/logs.zip)
I'm not precisely sure. 5-10 minutes. When I was watching, it appeared to be allocating around 50MB/second I'll try to time it
Memory usage of nightly build is holding steady at around 290 MB 
I spoke too soon. I left it running in the background while I worked on other things. It just hit 18GB  WTF is an idle Lapce process even doing...
Update: I have a memory dump of the 18GB process. I obviously can't share it both for size constraints and NDA reasons. However, if there is any summarization analysis I...