rdd3 writes:
1. less stable than alpha / random crashes
2. No longer able to inspect by flying over a value when debugging locally (can still do a watch).
3. Javascript dies within 10 minutes of editing in almost every session (even with "Auto list members" turned off, which is necessary to avoid having it hang/crash even sooner).
(i've asked him to send us his solution file)
Comments: Attached is a sample project to help in diagnosing issue #874 (I'm not sure this is any different from #661). Unfortunately I cannot provide my actual project (it's reasonably large and complex). The IP exposure would be too great. For this project, I just created a blank express project and added a few packages (similar to what I listed in my comment to #661) and the Ace editor js files. I deleted the node_modules directory to make the project small enough to upload. Just right click npm and select "Install Missing npm Modules" to get to a complete project. When you load this project you will see it use ~250Mb of memory (via Task Manager). If you begin typing code into the various modules you will start to see the memory go up dramatically. You will also see a lot of output under JS Language Services. I have found that typing the beginning of a require statement, like this: var mod = require(' will drive memory to ~900Mb and produce lots of JSLS output. If I go add a simple exported function to each of the route modules, maybe a simple function or two in app.js, I'll be up to ~2Gb of memory. I can't get it to crash, but in my real project (which is quite a bit more complex), it gets to ~3.5Gb before it finally crashes So this might very well be the same issue - given that it's this bad with what is essentially a "Hello World" node.js app. Also, FWIW, hover inspection during debug doesn't work on this project (or at all, as far as I can tell).
1. less stable than alpha / random crashes
2. No longer able to inspect by flying over a value when debugging locally (can still do a watch).
3. Javascript dies within 10 minutes of editing in almost every session (even with "Auto list members" turned off, which is necessary to avoid having it hang/crash even sooner).
(i've asked him to send us his solution file)
Comments: Attached is a sample project to help in diagnosing issue #874 (I'm not sure this is any different from #661). Unfortunately I cannot provide my actual project (it's reasonably large and complex). The IP exposure would be too great. For this project, I just created a blank express project and added a few packages (similar to what I listed in my comment to #661) and the Ace editor js files. I deleted the node_modules directory to make the project small enough to upload. Just right click npm and select "Install Missing npm Modules" to get to a complete project. When you load this project you will see it use ~250Mb of memory (via Task Manager). If you begin typing code into the various modules you will start to see the memory go up dramatically. You will also see a lot of output under JS Language Services. I have found that typing the beginning of a require statement, like this: var mod = require(' will drive memory to ~900Mb and produce lots of JSLS output. If I go add a simple exported function to each of the route modules, maybe a simple function or two in app.js, I'll be up to ~2Gb of memory. I can't get it to crash, but in my real project (which is quite a bit more complex), it gets to ~3.5Gb before it finally crashes So this might very well be the same issue - given that it's this bad with what is essentially a "Hello World" node.js app. Also, FWIW, hover inspection during debug doesn't work on this project (or at all, as far as I can tell).