Same thing without colorer. It is just different script that is last line before crash. This one:
MHTools.Loot Helpers are ready: VM29:598 > Object
In initial post I mentioned that TACS works without crashes. So it is something in TABS that makes Chrome freak out.
I use Linux version of Chrome, and the message in the tab is "SIGKILL" with button to "Reload". When pressed it will load game again. Windows version may do something slightly different, so people see login screen, or they start with login screen, not direct link?
Also, I left game with view of next camp I will attack, while scribbling this. It did not crash. I guess I have to catch what kind of interaction with TABS breaks game.
@nefrontheone this behavior is similar to what you are experiencing in chrome on mac. But you said it was not script related. @Danpodan yes try to understand which function causes the crash (maybe high number of cached simulations?). On Windows i can't reproduce the problem.
Yes a have same crash in Chrome for Mac, can't test in Windows now.
But the error is not relate to TABS, remember I use TACS. ;-)
In the past I deactivated Tamper, all extension, all scripts and crash is coming time to time...
Maybe the problem is related to Chrome or a misuse of system memory. :-?
I'm testing with the game's animations, effects and graphical enhancements disabled (as someone commented on the forum) and the error takes a long time to occur.
Edited:
A few minutes after activate animations, effects... the result was:
Not a part of EA / Envision teams - My comments are only mine.
@ o0netquik0o (maybe high number of cached simulations?).
Same thought here. Before it crashed it showed 24 cashed attacks - next was crash. So I tried few attacks on smaller camps that don't require much rethinking and it did not crash. Today I'll try to use "reset" function to keep cached number low, and if that works, next is to see how to increase memory.
BTW, is it possible that memory assignment is automatic - as much as script asks? This is first time I deal with this so forgive me that I have no clue how it works.
@ nefrontheone Exactly the same. Error 5 is most likely equivalent of SIGKILL.
MacOS is derivative of, or based on Free BSD, which works similar as Linux. Ditto, we see different actions than Windows.
it just crashed on 3rd simulation stored, but it did not few camps in the row where I collected from 10 to 20 simulations. Options why it happens are growing in number; time for paper and pen.
@Danpodan Are you sure that the crash does not happen without TABS or/and without scripts enabled? Surely cached sims raise the amount of memory footage for the browser tab but it should not crash. Also i saw 2 updates for chrome recently for WIndows. Be sure to update to last version. LEt me know what you find out.Also do you tried disabling graphic effects like @nefrontheone said previously?. Bye
I frequently leave game running alone with all bells and whistles. It doesn't crash.
The only recent anomaly is that main game screen (map) is unresponsive after long period of inactivity. It needed restart to accept commands.
Right now I have to find the way to read system logs, to see who sent SIGKILL. I quit playing with Linux long ago, and become just its user, so it will take some time to relearn how it works this days.
Will these updates fix the memory error in the browser?
Also how do I add the gethub file into SoO script pack?
Sorry to say but no. Memory issue are not strictly related to scripts codes. Maybe can be related to known bug introduced in Chromium code on July. You can read more about here.
for the second question... actually the most recent codes is integrated in last version of the pack. The lasat update not yet available on Chrome and Edge does not change the operating functions of scripts on these platforms. Only Opera users are affected by a bug i hope to have fixed in 1.6.3.
Any way there is a "trick" you can use to have updated scripts working in extension before it is updated by me.
for temporary fixes you can always fiddle around and just copy and overwrite the script file
xxxxxx.user.js
in
C:\Users\[USERNAME]\AppData\Local\Google\Chrome\User Data\Default\Extensions\mhohhaneodmbojhibocihibkiiafigkl\1.x.x_0\scripts
where [USERNAME] is your windows username profile and x are script name and extension version installed.
You will not see updated version numbering in options but you will use updated code.
Replies
MHTools.Loot Helpers are ready: VM29:598
> Object
In initial post I mentioned that TACS works without crashes. So it is something in TABS that makes Chrome freak out.
I use Linux version of Chrome, and the message in the tab is "SIGKILL" with button to "Reload". When pressed it will load game again. Windows version may do something slightly different, so people see login screen, or they start with login screen, not direct link?
Also, I left game with view of next camp I will attack, while scribbling this. It did not crash. I guess I have to catch what kind of interaction with TABS breaks game.
But the error is not relate to TABS, remember I use TACS. ;-)
In the past I deactivated Tamper, all extension, all scripts and crash is coming time to time...
Maybe the problem is related to Chrome or a misuse of system memory. :-?
I'm testing with the game's animations, effects and graphical enhancements disabled (as someone commented on the forum) and the error takes a long time to occur.
Edited:
A few minutes after activate animations, effects... the result was:
Same thought here. Before it crashed it showed 24 cashed attacks - next was crash. So I tried few attacks on smaller camps that don't require much rethinking and it did not crash. Today I'll try to use "reset" function to keep cached number low, and if that works, next is to see how to increase memory.
BTW, is it possible that memory assignment is automatic - as much as script asks? This is first time I deal with this so forgive me that I have no clue how it works.
@ nefrontheone
Exactly the same. Error 5 is most likely equivalent of SIGKILL.
MacOS is derivative of, or based on Free BSD, which works similar as Linux. Ditto, we see different actions than Windows.
The only recent anomaly is that main game screen (map) is unresponsive after long period of inactivity. It needed restart to accept commands.
Right now I have to find the way to read system logs, to see who sent SIGKILL. I quit playing with Linux long ago, and become just its user, so it will take some time to relearn how it works this days.
No, the comment is not from me, it was from @Morticer
Also how do I add the gethub file into SoO script pack?
Sorry to say but no. Memory issue are not strictly related to scripts codes. Maybe can be related to known bug introduced in Chromium code on July. You can read more about here.
https://forums.ea.com/en/commandandconquer/discussion/276593/chrome-not-enough-memory-to-open-this-page#latest
for the second question... actually the most recent codes is integrated in last version of the pack. The lasat update not yet available on Chrome and Edge does not change the operating functions of scripts on these platforms. Only Opera users are affected by a bug i hope to have fixed in 1.6.3.
Any way there is a "trick" you can use to have updated scripts working in extension before it is updated by me.
for temporary fixes you can always fiddle around and just copy and overwrite the script file
xxxxxx.user.js
in
C:\Users\[USERNAME]\AppData\Local\Google\Chrome\User Data\Default\Extensions\mhohhaneodmbojhibocihibkiiafigkl\1.x.x_0\scripts
where [USERNAME] is your windows username profile and x are script name and extension version installed.
You will not see updated version numbering in options but you will use updated code.