On Thu, May 3, 2018 at 3:13 PM, Holger Freyther <hol...@freyther.de> wrote:
> I am facing a problem with the new SessionManager>>#snapshot:andQuit: > code. I have had plenty Pharo70 images that didn't restore anymore as the > code is waiting for the "wait" semaphore. For sure it is something my code > is doing but could anyone think of ways to make it more robust and handle > failures more gracefully? My main concerns are: > > * When the failure becomes noticeable it is too late. :( > * It fails silently. Maybe WorkingSession>>#runStartup: shouldn't rely on > the UIManager doing the right thing (before the UI was fully initialized?) > * Debugging is hard, there is no indication of why it broke, and getting > to the situation of breakage takes a bit of time (installing the > baseline..). > Can you give me more details about how to reproduce it? You're loading a baseline as a startup action? As a startup script? > > holger > > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13
