I was wondering if I could have kill manually this process, but the
process browser does not let you do that mistake.
Thanks for the tip.
Le 21/09/2016 à 12:11, Guille Polito a écrit :
> Hi Hilaire, all,
> I started digging this morning on this issue, and I see why we can have
> such problems.
> Apparently, there is some strange case that produces a bug in UIManager.
> To explain it with code, the UIManager should satisfy allways the
> following invariant.
> "If executed from a workspace/playground. i.e., the UI process itself:"
> UIManager default uiProcess == Processor activeProcess. => true
> Somehow, in the image you provided me, it is not the case.
> I'm still taking a look at what would cause this. And I also think we
> still have this bug in pharo 6 (and thus pharo 5) because I found it
> lately very often.
> In the meantime, if you find that your image is causing you these
> problems, you can workaround it by executing:
> UIManager default spawnNewProcess.
> Once you do that, the ui process should come back to a correct state and
> the debugger should behave as expected.