-
Notifications
You must be signed in to change notification settings - Fork 93
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
Odd hang behavior; hard to replicate #305
Comments
I believe that exceptions raised in threads by agents are unreported unless one sets up appropriate error handlers... which I thought we had done correctly in Clojush, but perhaps you have discovered a gap in our handling of this. |
I don't even know how you could instrument that so an error was caught. |
Is there any reason why the |
I'm still seeing this problem, mainly with this particular demo file. But that might be because I keep trying to evolve solutions with it. I suppose there might be a problem with the definitions or the settings. How can I even find out? |
I've made some edits and removed (1) the newly registered problem-specific instructions, and (2) the Help me understand if there was a bug in the code I had added (it's old), or if there's a Clojush bug involving problem-specific instructions and/or |
I've been running some very long, sort of large runs on a desktop machine. In several runs the search has gotten a few generations, and then hung. No error, no crash, just "Processing generation: X" for 20+ hours, for random X.
When I glance at Activity Monitor, there are no Java processes running. Is it possible for the JVM to crash without an error message? If so...
¯\_(ツ)_/¯
The text was updated successfully, but these errors were encountered: