Was this fixed? I'm debugging unit tests and I'm getting an infinte loop everytime a MNU is triggered.
MessageNotUnderstood: receiver of "new" is nil UndefinedObject(Object)>>doesNotUnderstand: #new Message>>sentTo: UndefinedObject(Object)>>doesNotUnderstand: #new Message>>sentTo: VM: Unix built on May 4 2016 11:54:41 Compiler: 4.6.3 CoInterpreter VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 https://github.com/pharo-project/pharo-vm.git Commit: b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 Jenkins build #589 Image: 6521 Best regards, Esteban A. Maringolo 2016-09-21 15:01 GMT-03:00 Hilaire <hila...@drgeo.eu>: > Hi Guille, > > 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. > > Hilaire > > 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. >> >> Guille > > -- > Dr. Geo > http://drgeo.eu > >
