sgithens
commented
3 months ago This is a good question. Assuming it's reproducible, or even mildly reproducible, I'd recommend:
- Taking a screen of the full window and including it (assuming there isn't any private/personal data on it)
- Attach the microworld .box file if you can (unless it's one of the examples checked in to github, then you could just reference it and it's version. Or still upload it if that's easier)
- Describe as best you can what you were doing. Especially if you may have been doing some sort of input, or resizing the window, or evaluating a particular line, or resizing the window WHILE evaluating a line. etc.
- And then comment on how reproducible it is... always happens, intermittent, etc.
Hopefully this helps a bit...
I am considering adding an advanced/debug menu option on a future version to pop open the lisp repl, in case I needed more information.
Sometimes I'll do something and Boxer will hang. It looks like this:
No Common Lisp exception is shown. No Terminal window automatically appears with information about Common Lisp's state.
Is there a way to collect data that would be useful for reporting such hangs?