Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profiler nests non-recursive functions #351

Open
arvid220u opened this issue Jan 17, 2020 · 2 comments
Open

Profiler nests non-recursive functions #351

arvid220u opened this issue Jan 17, 2020 · 2 comments
Labels

Comments

@arvid220u
Copy link
Contributor

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.

@arvid220u
Copy link
Contributor Author

@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
Copy link
Contributor

jmerle commented 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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants