whoa! stdout explosion in DrRacketCS
28 views
Skip to first unread message
John Clements
Jun 12, 2020, 1:36:35 AM6/12/20
to Racket Developers
About two minutes ago I hit “save” on an unsaved buffer in DrRacketCS on Mac running MacOS Catalina 10.15.5, was surprised to see a spinning beach ball for a few seconds, then went to the terminal from which I’d started DrRacket and saw this:
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handle
… this was being generated very very quickly, megabytes per minute, surely. I force quit (at the OS level).
The catch is that I’m running a version of DrRacketCS that dates back to May 25th, and it looks like some maybe-possibly-related fixes have happened since then, so I’ll update and for now this is just an FYI.
John
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handler: #<procedure>: arity mismatch;
the expected number of arguments does not match the given number
expected: 1
given: 0; original exception raised: exception raised by error display handler: invalid memory reference. Some debugging context lost; original exception raised: exception raised by error escape handle
… this was being generated very very quickly, megabytes per minute, surely. I force quit (at the OS level).
The catch is that I’m running a version of DrRacketCS that dates back to May 25th, and it looks like some maybe-possibly-related fixes have happened since then, so I’ll update and for now this is just an FYI.
John
Reply all
Reply to author
Forward
0 new messages