Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#780 Memory Issues

Bug
open
Neil Hodgson
SciTE (622)
5
2009-03-31
2009-03-30
rainingcurses
No

After running SciTE for a long time on a log file that updates very often. I find that the memory usage gets VERY high. We are talking over 1GB of VM Memory being used, which of course makes the page file very large and massively affect PC performance.

I found this problem is version 1.71, I don't know if it has been addressed yet or not. I have downloaded the latest version and will report back if the problem is still there, please let me know if it has been fixed already.

Discussion

  • rainingcurses
    rainingcurses
    2009-03-30

     
    Attachments
  • rainingcurses
    rainingcurses
    2009-03-30

    I can confirm - it seems that this problem is still present in 1.77

    I have attached a screenshot of task manager. The memeory went that high after I ran many reloads (CTRL + R) of 1 single file, there were no changes made to the file in between reloads, I just pressed ( CTRL + R ) many times to replicate the problem that I get over a long period of having SciTE open.

     
  • Neil Hodgson
    Neil Hodgson
    2009-03-31

    • assigned_to: nobody --> nyamatongwe
     
  • Neil Hodgson
    Neil Hodgson
    2009-03-31

    How big is the file? It is normal for SciTE to use more than double the file size in RAM. What settings have you changed from the defaults?

     
  • rainingcurses
    rainingcurses
    2009-03-31

    I didn't make any changes to the settings after downloading 1.77, I was using the defaults.

    The file size was ~20MB. You should be able to replicate the problem by just opening a file around that size and holding CTRL + R ( or whatever you have reload shortcut set as ) if you hold it for a while with Task Manager open you can see the memory rise, and then after you stop reloading it never drops back down again until you close the tab that holds the file that you were refreshing.

    Thanks for the help.

     
  • Neil Hodgson
    Neil Hodgson
    2009-03-31

    Its retaining an undo history to allow you to undo the "Revert". You could implement an equivalent to "reload.preserves.undo" for Revert. For source code, undoing Revert is useful.

     
  • rainingcurses
    rainingcurses
    2009-03-31

    OK that makes sense. Kind of, CTRL + R is reload from disk right? What is "Revert"?

    Do you mean to say it's something I can turn off with a setting in the properties file?

    I set reload.preserves.undo=0 in the global properties file, but I still have the same issue with it using lots of memory :(

     
  • Neil Hodgson
    Neil Hodgson
    2009-04-01

    The Revert command is in the File menu and is bound to Ctrl+R. It reverts the file contents to what is on disk which, unless another process changes the file, means revert to the last saved version. Reload occurs automatically when load.on.activate=1, the file has changed on disk and focus switches to SciTE. reload.preserves.undo is only for reload, not for revert.

    Stopping revert from preserving undo would require implementing a new setting revert.preserves.undo.

     
  • rainingcurses
    rainingcurses
    2009-04-02

    Would it be easy to implement a new setting? Is it something that you could add for me, as a patch or something like that?

    I would add it myself, but I think it may be beyond me as I only really know java.

     
  • Neil Hodgson
    Neil Hodgson
    2009-04-03

    In open source, features are mostly implemented by the person that wants it enough to do the work. If you can't do it yourself, you could try to interest others in implementing this by writing to the feature request tracker or the mailing list but I don't expect there would be any volunteers. It would be fairly simple to add but its not been enough of a problem for anyone to notice it before.