I ve'seen this problem also but never been able to find a reproducible case. I've recall to see it even before Iceberg, so to me it looks like some Monticello issue. I always had the impression that Monticello it's trying to regenerate all the code definitions instead of the changes. Running exactly the same code snippet again usually worked for me.
Anyways if someone had a reproducible case just let us know. On Fri, Aug 24, 2018 at 2:03 PM Sean P. DeNigris <[email protected]> wrote: > Sometimes while working in Iceberg on 6.1, I see a progress bar(s) like the > following: > <http://forum.world.st/file/t128965/Screenshot_2018-08-24_12.jpeg> > > This seems to usually signal that a crash is not far away. It's doubly > concerning because there is no clear way to stop the troubled process > (interrupts often bring up a debugger on something else) and because, since > one is now unable to save any code, it's unclear how to start over easily > in > a new image. In an extreme scenario, I recently panicked during such an > experience and accidentally clicked "Save" instead of "Save As…" resulting > in an image that took hours worth of code (I know maybe not a great > practice) with it to the grave. > > Any idea why this happens or what we might be able to do anything about it? > > p.s. I was so concerned that I immediately resolved to move to Pharo 7, but > that turned out not to be an option do to the recently reported bug with > extension methods (that don't exactly match the package name) > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >
