Quote:
Not Solved, Warning still appears in my Logs
Can you use the "take out half the OXPs" trick to narrow it down to a particular one?
Quote:
While it's certainly possible, I'd be somewhat surprised if the garbage collected timers were actually a causal factor in the crashes.
I would be very surprised indeed: the warning is mostly to the OXP writer who might otherwise be confused about why their timer stopped working (or continued working after they thought it should have stopped, since garbage collection is a relatively rare event). The game then does the clean up the writer should have done.
It's very rare that the last entry in the log in the case of a full crash has anything to do with the crash at all: usually it just puts the blame on the most talkative OXP. Unless the timestamp on the message was within a few hundreths of a second of the crash at most, it's almost certainly entirely unrelated. Generally when the game's going to crash it doesn't have time to say why. (Which isn't to say the Latest.log is useless, just that it's not that useful).
Quote:
Where it says function: anonymous I'm assuming it's referring to the function that created it... How about making it report the function it calls? It has to know the name of the function it's calling even if the function itself is no longer valid...
It's the function it calls. But not all functions
have names.
Code:
var t = new Timer(this, function() { this.ship.commsMessage("Help!"); }.bind(this), 0.5, 5);