Just gonna share what I wrote in a different post here:
the new NW.js finally works with Klang, and oh boy does it work as advertised! Way smoother performance, and areas I felt needed optimizing now runs butter smooth. Don't seem to notice any lagspikes after prolonged play.
HOWEVER... I keep getting the occational 100ms (approx) lagspike consistently. I can only guess this is due to the more aggressive garbage collection? I really love the fact that the game now won't turn into a slideshow after playing for too long, but these lagspikes will ruin the player's sense of rhythm. It's crucial that I find a way around this, or that the garbage collection becomes more flexible.
I'm curious if anyone knows what's usually the biggest offenders with gathering garbage for construct games? Does continiously creating and destroying objects matter for instance? If I know what to look out for I can maybe work around it myself.
Did some more testing. This time on my laptop. The results were interesting to say the least.
The first thing is that I couldn't get the game to boot choosing the nVidia GPU (630m) even with the latest driver installed. This used to work before on NW 12.
Running the game on the intergrated card worked fine though. However the loading times was greatly increased. in-game videos wouldn't play properly etc. I noticed lagspikes even where I'm 100% certain there ain't any new items loading in. When I played long enough though things started to change. When playing for long enough for the stutter to kick in on NW 12, I now experienced that everything ran smooth, way less lagspikes, and no loading issues. The videos that previously didn't play properly now worked as intended etc.