Smalltalk › Pharo › Pharo Smalltalk Developers

Pharo 6 image lockup at startup

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Thierry Goubier

Pharo 6 image lockup at startup

Hi guys,

It seems there is a strange interaction between the deprecation rewriter and image startup.

If you load a package that has deprecated calls (command line loading: without GUI), then save the image, the image will appear locked on the next interactive start (black background on Linux).

Loading the package by hand in an interactive image and saving a new version with the deprecation rewritten solves the problem.

Thierry

stepharo

Re: Pharo 6 image lockup at startup

Thanks for the bug report.

Marcus is on vacation now (like me - I will start to integrate more
issues as soon as I get a better network - here it is quite quite slow
;) and he will certainly have a look when he is back.

Stef

Le 20/7/16 à 17:16, Thierry Goubier a écrit :

> Hi guys,
>
> It seems there is a strange interaction between the deprecation
> rewriter and image startup.
>
> If you load a package that has deprecated calls (command line loading:
> without GUI), then save the image, the image will appear locked on the
> next interactive start (black background on Linux).
>
> Loading the package by hand in an interactive image and saving a new
> version with the deprecation rewritten solves the problem.
>
> Thierry

Marcus Denker-4

Re: Pharo 6 image lockup at startup

In reply to this post by Thierry Goubier

Hi,

One problem we had is that source writing in shutdown (and I think startup, too) was not working, due to the strange InMidstOfFileinNotification, uh, trick.
(abusing an exception to emulate a kind of dynamic variable).

This now has been replace by having a #deferFlushDuring: on SourceFiles and using that for MC loading.

I think this might fix the problem.

> On 20 Jul 2016, at 17:16, Thierry Goubier <[hidden email]> wrote:
>
> Hi guys,
>
> It seems there is a strange interaction between the deprecation rewriter and image startup.
>
> If you load a package that has deprecated calls (command line loading: without GUI), then save the image, the image will appear locked on the next interactive start (black background on Linux).
>
> Loading the package by hand in an interactive image and saving a new version with the deprecation rewritten solves the problem.
>
> Thierry