On 24 Aug 2018, at 20:41, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
Le 24/08/2018 à 19:03, Sean P. DeNigris a écrit :
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)
Hi,
IIRC the problem only happens when the commit windows is maximize. Something happen, maybe the progress bar updating launch a redraw of the morph, and if the iceberg window is under the progress bar it also try to redraw it but for that it snapshots methods etc...
When I did not maximized my windows and kept them in the center it was fine.
Yes, afaik that problem was related with redrawing of some glamour lists and an infinite loop triggered by the old iceberg UI. Esteban
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
-- Cyril Ferlicot https://ferlicot.fr