Skip to main content
B i r n o u
B i r n o u
Legend
May 26, 2020
Question

would DW be prone to memory leaks?

  • May 26, 2020
  • 2 replies
  • 2237 views

hello,

 

randomly, let's say that I haven't yet identified the methodology to reproduce this behavior, DW increases its memory consumption considerably, and this in an unexplained way.

 

It happens very regularly.


As a result, DW becomes unusable, and the only way to work is to force DW to quit, to reboot everything.

 

Any idea, other than to employ another code editor 😉

have a pleasant day

birnou

 

 

      This topic has been closed for replies.

      2 replies

      pziecina
      pziecina
      Legend
      May 26, 2020

      Hi Birnou,

       

      This has become more common with adobe programs over the years. You will probably find that it is related to what Dw, (and other programs) are doing with the node.js 'watcher', for that program, which for some unknown reason Adobe has incorporated in many of its programs, (though I do have some suspicions as to the what node is doing and the why, sorry only suspitions, as I'm not interested enough to confirm).

       

      In discussions regarding other programs where similar to your question have been posted, node has been the reason. The problem though, is that disabling node often disables functionality, and / or causes the program to crash.

        BenPleysier
        Community Expert
        BenPleysierCommunity Expert
        Community Expert
        May 26, 2020

        Have a look at https://community.adobe.com/t5/get-started/process-called-node-exe-in-task-manager/td-p/9831224?page=1

         

        Interestingly, I am creating a project using NodeJS as we speak. So far, not as happy as with PHP. Perhaps it's the learning curve.

        Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!
          O
          osgood_
          Legend
          May 26, 2020

          Its probably the learning curve....you know once we know a workflow learning something else is always a pain until we know it well enough.

           

          I dont know how Wap handles  node but the comments I will make about node, if you are using a manual workflow:

           

          It's less developer friendly than php, asp, cold fusion etc. You have have to adhere to a strict file/folder structures. I have no idea why, it feels backwards rather than maintaining the status quo. A case in point I cant just point to a linked css file/asset, I have to tell the main app.js that its in a specific folder, the name of which doesnt get appended to the css file link, confusing and madness.

           

          I have to create all the page routes whereas in php the file is the route, so that means extra 'unwanted files', meaning more management.

           

          If I organise my modules into folders I have to export them then require them. In php you just include them.

           

          In php all the logic can be executed in the same file where in node I have to seperate the logic into independent files, madness, which means switching and opening folders and files constantly.

           

          You would want to use a template engine like ejs or handlebars which are equally as verbose as injecting php into your html, one of the main reasons why developers say they dont like php, so I just dont get it, all are not ideal.

           

          Ok I could go on but that's just my experience. Obviously node is useful for certain situations like like multi-threading, games, real time chat, auction, share dealing aps etc and if thats what your goal is in web-development you would use node, no ifs or buts. If your goal is more the front facing visual website with a CMS etc then youre probably better of using a less cumbersome workflow like php, asp, cold fusion.

           

           

           

          B i r n o u
          B i r n o uAuthor
          Legend
          May 26, 2020

          well, if the question arose, here is also the context of use at the time when memory consumption is running out of steam
          - code view only
          - just in case; the display tab is in create mode, although only the code tab is active.
          - only one PHP file and one javascript file are open
          - this is a work on a plug in for wordpress

          - wordpress is locally installed (at least I think, I didn't verify... youps... I will)
          - xamppv3.2.4 is launched

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices