I don't know. Maybe - there is a ProtoObject subclass involved
(DatabaseProxy, a class that proxies OmniBase objects across
transactions). But the image kept running and there's no debugger or
exception notification on the UI... However, the fact that processes
were suspended, and AFAICT the debugger is the most likely Suspender
Of Ye Processes, it might be worthwhile to take a look in that
direction.

Strangely enough, the image has been happily running the test site
ever since I got determined to really really get down to the issue...
The bug probably got scared...

On 10/12/05, Chris Muller <afunkyobject at yahoo.com> wrote:
> Hi Cees, you may have run into the "non-debuggerable" situation I asked about a
> while back..
>
>
> http://lists.squeakfoundation.org/pipermail/squeak-dev/2005-January/087592.html
>
> Unfortunately, I did not know how to fix it, sorry.
>
>  - Chris
>
> > Funny - I had the image running with the process browser open. Tonight
> > the thing hung again, I could Alt-. but although the debugger window
> > popped up, input wasn't accepted. Furthermore, the process browser was
> > full with suspended processes - I couldn't see any context because I
> > couldn't select a process, so I killed the image for another try...
> >
> > If anyone can shed a light on this, it'd be much appreciated :)
>
>