Repository navigation
Profiler nests non-recursive functions #351
Description
I'm guessing this appears because of a mismatch between addExitMethodHandler and addEnterMethodHandler — presumably either the first one is not called when it should be called, or the second one is called but shouldn't be called. Might it have to do with bots being cut off in the middle of computation without calling Clock.yield() because of the bytecode limit?
I have only seen this with one bot, which I sadly cannot put here since it is a competitor bot. So this isn't a huge issue I think.
Activity
arvid220u commentedon Jan 17, 2020
@jmerle If you have seen this error previously or know what it might be a result of then that'd be great — otherwise, I'd suggest we ignore this unless more people have the same problem.
jmerle commentedon Jan 17, 2020
I'm not able to reproduce this in any way, not even when intentionally going over the bytecode limit. Without example code it's really hard to guess what's going on here or to reproduce it, so I guess you can ignore it for now (or debug it yourself ofcourse).