The Welkin Suite Forum

[Fixed] Memory leak



[Fixed] Memory leak

  • Please log in to reply

#1

ikljaic

    Posted 29 Jul 2015

    I'm sorry, But I have to report that there is a memory leak again. after an hour I start spending about 400M of RAM



    8 replies to this topic

    #2

    ikljaic

      Posted 29 Jul 2015

      the version is 21.6



      #3

      vlgubanovich

        Posted 29 Jul 2015

        Hi ikljaic,


        400MB RAM is generally normal memory consumption (of course in case if it doesn't become 800MB in some hours).


        Code analysis information that is used for all Code Assistance features is mostly stored in RAM in order to provide quickest access. Also opened code editor tabs are consuming 10-30MB ram each one (in average).


        So generally 300-400MB is an average that we try to stick with. In case if you have not the smallest project, if you have Test Results panel opened and multiple opened editor windows - this is totally ok.


        But if memory consumption increases without no actions from your side or if it raises more than 600-700MB - this may be a place for us to investigate.


        Anyway thanks for letting us now.

        Vladimir


        Vladimir Gubanovich
        Head of Product
         
        The Welkin Suite
        skype id: vladimir.gubanovich
        e-mail: vladimir.gubanovich@welkinsuite.com


        #4

        ikljaic

          Posted 29 Jul 2015

          Welll, ... 300 was the beginning. yesterday I left it open on my home PC. When I came home It was using abou 1G. :P



          #5

          vlgubanovich

            Posted 29 Jul 2015

            Wow. Not good. I'd say not good at all.


            If you don't mind I'll ask you some (unfortunately - many, not some...) questions in order for us to understand what may be the reason:

            1. How many (+-) files there's in a project? And how many of them are .cls files?
            2. How many editor tabs are opened?
            3. If you've run unit tests - is there a lot of test jobs in Test Results?
            4. Do you have code coverage highlighting enabled?
            5. Do you have logs window displayed (and logs polling)?
            6. Have you closed/opened different project(s) within a session?
            7. Have you executed Anonymous Apex or SOQL requests within a session? If yes - was it "very much requests", "many", "some"?

            Or maybe if you'll be able to describe (shortly) what were your activities during the session?


            Sorry for such a big number of questions, but we're really very surprised in a leak after previous release and need to localize this as precise as possible.


            Thanks,

            Vladimir


            Vladimir Gubanovich
            Head of Product
             
            The Welkin Suite
            skype id: vladimir.gubanovich
            e-mail: vladimir.gubanovich@welkinsuite.com


            #6

            ikljaic

              Posted 30 Jul 2015

              1) 3600 files, 800 classes

              2) always 2-5 max

              3) 1-2 max

              4) no, never got it to work

              5) no

              6) no. I always close it before opening a new one

              7) no, still do it with the dev console


              No problem. I know how hard it is to find bugs with no debug possibilities and I am glad to help. After all I work with salesforce and have this problem everyday :D:D:D



              #7

              stjepan.pavuna

                Posted 05 Aug 2015

                Hi all, just wanted to bring another case of memory leak here - in my case super extreme.


                Just opened Welkin Suite is using around 118K


                When I open my project (only code files, not full project) - it gets to 220k and from then onwards it grows each second by 2-3k. It does not stop - ever. This is brand new project, just pulled, nothing was executed, modified, saved back to the system, nothing.


                Here is my info:


                1. 306 .cls files, 30 components, 115 objects, 114 pages, 22 triggers, and some static resources
                2. With 5 classes opened, the growth was huge. With just one opened, growth is there as well. with all closed, memory size is fluctuating, but not growing. (grows up and down by 200k in few seconds)
                3. no tests run
                4. Only default settings on (nothing changed), did not find or change this one
                5. It is there yes, as in the default interface (I did no changes)
                6. Yes, but same thing if I close welkin and open it again and open a new project/solution
                7. Not at all.

                 

                For me Welkin is completely unusable, since it fills my memory in matter of minutes if I try to do any kind of work. The whole interface becomes laggy and unusable.



                #8

                vlgubanovich

                  Posted 13 Aug 2015

                  Hi stjepan.pavuna, ikljaic,


                  In this update (0.21.13.4) we've done serious improvements to the Apex grammar that we're using. We've found that previously it has lead to an excessive CPU load and sometimes to the RAM issues. The reason for this were incorrect rules which in rare cases resulted in infinite attempts to parse Apex files.


                  I'd kindly ask you to let me know if your situation with memory leaks is better now.


                  Thanks,

                  Vladimir


                  Vladimir Gubanovich
                  Head of Product
                   
                  The Welkin Suite
                  skype id: vladimir.gubanovich
                  e-mail: vladimir.gubanovich@welkinsuite.com


                  #9

                  vlgubanovich

                    Posted 13 Aug 2015

                    No problem. I know how hard it is to find bugs with no debug possibilities and I am glad to help. After all I work with salesforce and have this problem everyday :D:D:D


                    We have some great plans for bringing better debugging possibilities (even without Interactive Debugging from SFDC) :) But the only thing that I can say now is that we aim to get this done before 2016.


                    Thanks for your patience!


                    Vladimir


                    Vladimir Gubanovich
                    Head of Product
                     
                    The Welkin Suite
                    skype id: vladimir.gubanovich
                    e-mail: vladimir.gubanovich@welkinsuite.com


                    Boost Your Productivity. Get Started Today

                    Try Free Trial