- Status Closed
- Percent Complete
- Task Type Bug melden / Report Bug
- Category ISN AutoIt Studio
-
Assigned To
Christian Faderl - Operating System Windows 7 (64 Bit)
- Severity High
- Priority Very Low
- Reported Version 1.03
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: ISN AutoIt Studio - English
Opened by Rex - 10.12.2016
Last edited by Christian Faderl - 06.04.2017
Opened by Rex - 10.12.2016
Last edited by Christian Faderl - 06.04.2017
FS#248 - Studio uses a lot of ram, and cpu
I now think I know why I have the save problem, from time to time As you can see in my screenshot here, the script is launched but not saved http://prnt.sc/delsgl the studio uses a lot of ram, it spikes from around 800mb http://prntscr.com/dhskmz to over 1.5GB http://prntscr.com/dhsl0k :o And the cpu load spikes from 01 to 13-15. I know that my code is quite huge, almost 4500 lines of code - but in SciTE I only have a ram usage of ~50mb Cheers /Rex
I closed the studio, and reopened my script, and now the mem usage is normal again.
But i forgot to mention that I had the project open for 24+ hours, and I can see that it has created backups for every 10 min (as set to in settings).
Could it be some $var in the studio that, doesn't get cleaned up?
Cheers
/Rex
Hi Rex!
Wow..1.5GB..sound´s like a new record :P :P
And it looks like the ISN stucks in some loop...this would explain the persistent CPU usage.
I will try to reproduce this. If you have new infos with this, please let me know ;)
Hi Christian
Yeah 1.5GB ram is quit much, even for a large script :D
All i can remember so far, is that at some point during the night when I was working, the studio started to write that it had backup-ed 16 or so files, though there's only 2 in the backup folder.
Also some times the respond time was very long, but that I guess is be course of the cpu/ram usage.
And that annoying not saving when running script thing, that's keeps coming back.
Cheers
/Rex
For the notes: In the next update (1.04) the CPU usage (in idle) should be much lower than in 1.03.
I will close this task now. The new update (1.04) is released today.
If the problem still exists, please make a new task.
Thanks