stuck in critical section (Monitor)
RossBoylan at stanfordalumni.org
Sat Apr 20 00:41:33 UTC 2002
Here's another oddity/clue: the background update process has asOop
of a number that doesn't match any of the listed processes in the
process browser, even after updating the latter.
(asOop seems to match the process numbers in general, but I'm not
completely sure it's what ProcessBrowser is using).
The background process was the one I suspected I killed when a
debugger popped up with an error.
So what does it mean to have a Process that doesn't appear in the
process browser? Has the scheduler lost track of it? Does this mean
it won't run?
More information about the Squeak-dev