Alek Posted March 11, 2017 Author Share Posted March 11, 2017 9 hours ago, DrDu said: not sure why the new client keeps maxing out memory for me It's a problem with your script then, I can't just wave my magic memory wand and add more memory usage. If it's an SDN script pm me and I may have time to look at it. Quote Link to comment
irwtonrs1 Posted March 11, 2017 Share Posted March 11, 2017 16 minutes ago, Alek said: It's a problem with your script then, I can't just wave my magic memory wand and add more memory usage. If it's an SDN script pm me and I may have time to look at it. For what its worth, my clients would also shoot up to 1GB just as his did on .118 whereas it wasn't doing it on the previous version. Had to use -mem to fix. So maybe it's not his script and rather the new client version, just saying. 1 Quote Link to comment
DrDu Posted March 11, 2017 Share Posted March 11, 2017 1 hour ago, irwtonrs1 said: For what its worth, my clients would also shoot up to 1GB just as his did on .118 whereas it wasn't doing it on the previous version. Had to use -mem to fix. So maybe it's not his script and rather the new client version, just saying. what mem flag are you using and what mb is it? Quote Link to comment
irwtonrs1 Posted March 11, 2017 Share Posted March 11, 2017 3 minutes ago, DrDu said: what mem flag are you using and what mb is it? -mem 512 Quote Link to comment
Alek Posted March 11, 2017 Author Share Posted March 11, 2017 1 hour ago, irwtonrs1 said: For what its worth, my clients would also shoot up to 1GB just as his did on .118 whereas it wasn't doing it on the previous version. Had to use -mem to fix. So maybe it's not his script and rather the new client version, just saying. Your jvm was probably being constrained to 512mb, forcing gc. Once again I can't wave my magic wand and increase memory usage. Quote Link to comment
DrDu Posted March 11, 2017 Share Posted March 11, 2017 26 minutes ago, Alek said: Your jvm was probably being constrained to 512mb, forcing gc. Once again I can't wave my magic wand and increase memory usage. 28 minutes ago, irwtonrs1 said: -mem 512 im doing -256 and its low af now, been running for 1.5hrs Quote Link to comment
Alek Posted March 11, 2017 Author Share Posted March 11, 2017 6 minutes ago, DrDu said: im doing -256 and its low af now, been running for 1.5hrs Might as well set it to -mem 1 and let the magic memory system run OSBot on a single megabyte. 4 Quote Link to comment
DrDu Posted March 11, 2017 Share Posted March 11, 2017 11 minutes ago, Alek said: Might as well set it to -mem 1 and let the magic memory system run OSBot on a single megabyte. wtf, can i do negative? magic Quote Link to comment
pipez Posted March 11, 2017 Share Posted March 11, 2017 so the client should be us ing less CPU now? 1 Quote Link to comment
Developer Zach Posted March 11, 2017 Developer Share Posted March 11, 2017 10 hours ago, irwtonrs1 said: For what its worth, my clients would also shoot up to 1GB just as his did on .118 whereas it wasn't doing it on the previous version. Had to use -mem to fix. So maybe it's not his script and rather the new client version, just saying. I've looked into the issue and doubt it's the new client doing it. Looks more like Java is now being allowed to do it's thing instead of forcing it to live with lower memory than optimal. Quote Link to comment
Tom Posted March 12, 2017 Share Posted March 12, 2017 16 hours ago, Alek said: Might as well set it to -mem 1 and let the magic memory system run OSBot on a single megabyte. Have you ever considered doing standup? 6 Quote Link to comment
Ship Posted March 24, 2017 Share Posted March 24, 2017 Who in the world has less than 1gb of ram in 2017 lol Quote Link to comment
