I'm not sure if that's everyone's problem, but it sounds likely it might be related. Whether that's due to a file, file name, number of files, I have no idea. So my scientific conclusion on this after ten minutes of research is: the node process is choking on my large dev server directory, which is 1.62GB and has 25,115 items in it. Just switched back to the original much larger site directory, and it's back to ~120% CPU and fans are churning away.

Switched to a few other sites, and not seeing much CPU usage. I just switched to a much smaller site in the Files panel, and this all stopped. It seems to drop away and come back periodically under a different process ID, so not sure if it keeps starting over or what. When I click on the process and look at open ports and files, it seems to be traversing my entire local site files list. Guess how many windows are open in all three combined? Zero.Ĭheck Activity Monitor, and Dreamweaver is churning away at ~120% CPU, by far the most active process (node).

Click on the battery and see under Using Significant Energy: Adobe Dreamweaver, Adobe Photoshop, Adobe Illustrator. Sitting here wondering why my Mac won't quiet down as I'm not doing anything actively since waking it up. I may be able to trigger this problem simply by switching DW back to 'Site B'.Īdding to the thread too. Please contact me by PM if there's anything I can do from here. so I have a strong interest in proactively solving this mystery beforehand. I don't use Device Preview, either.Įventually, I'm going to need to work on 'Site B' -and even-more neglected 'Site C' and 'Site D' etc. I have no idea how this applies as I don't use any css preprocessor commands. Note: I briefly read the wikipedia descriptions of 'less' and 'sass' but that's all I know. In the thread above you (Niharika Gupta) said 'We use Node to compile less/sass files and for Device Preview.' Could you say a bit more? Is it possible that Node encountered difficulties scanning and processing 'Site B'? Maybe Node would eventually complete the scan, but it might take many minutes or even hours? (A good excuse to go out for a long lunch?) My 'Site A' was up to date, so there was no need to scan it at all. 'Site B' was far out of date -and there has been one DW revision, maybe two- since I last opened it, so DW needed to do a complete local scan. If s omething is far out of date, DW will scan the entire local site to make it current. CPU use is 'normal'.įrom my point of view, it appears that DW is maintaining something for each site. A few seconds later, process 'node' disappeared from the task list and has not reappeared in the last hour. I finally succeeding in banishing process 'node' by doing this: I switched DW back to 'Site A', a much larger site which I edit every day. Since then, I updated MacOS to 10.12.6, and -yes- I restarted the Mac to do that. In the last several days I updated DW to the latest version. (The last time I edited anything in 'Site B' was 4 months ago.) I viewed a directory on the server (remote) 'Site B', viewed the local version of the same directory, then left DW to do something else. What did I do most recently in DW? In the last hour or so I closed all open files and I switched to 'Site B', which I work on very rarely. I was using the Finder, Preview, and LibreOffice to organize files, that's all. What was I doing in DW at the time? Nothing. The process seemed to be scanning the entire local file tree of 'Site B' - which I work on very rarely. Then a new process of the same name would be created, and so on.Įventually I got a capture of 'Open Files and Ports' data. Tried to look at 'Open Files and Ports', but this was difficult because it appears that a process of this name would be spawned, would run for some small number of seconds and would terminate, deleting 'Open Files and Ports'. Tried 'get info' on the 'node' process, found its parent was DW. Noticed unusually heavy CPU usage in Activity Monitor, investigated, found process 'node' was using 100%+ of a CPU.

Adobe dreamweaver cc 2017 beginner