Sean P. DeNigris writes:
> For "Issue 16115: Launcher: Update Common Tools for Moose 5.1 Release"
> (https://pharo.fogbugz.com/default.asp?16115), the fix has been picked up by
> the CI and I verified that it works. What is the process here? Shall I close
> the issue with something like "in buil
Hi
I am using *SystemWindow* to open a Morph in my application *searchQuick*.
( https://github.com/jig08/sQuick_new )
On clicking a button, a new screen opens up but the prev window fails to
close, though I have tried using #close methods.
The code snippets are as:
*--
On 08/07/2015 01:08 AM, Christophe Demarey wrote:
Le 6 août 2015 à 22:49, Dale Henrichs a écrit :
For the Metacello tests themselves, the version of Metacello under test is installed on
top of the version present in the image, using the "standard Metacello update
code" ... failures at this
For "Issue 16115: Launcher: Update Common Tools for Moose 5.1 Release"
(https://pharo.fogbugz.com/default.asp?16115), the fix has been picked up by
the CI and I verified that it works. What is the process here? Shall I close
the issue with something like "in build #51"?
-
Cheers,
Sean
--
Vie
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: b4ae22fb9850c70cf7eb0423f68f0e0a8293e738
https://github.com/pharo-project/pharo-core/commit/b4ae22fb9850c70cf7eb0423f68f0e0a8293e738
Author: Jenkins Build Server
Date: 2015-08-07 (Fri, 07 Aug 2015
Branch: refs/tags/50213
Home: https://github.com/pharo-project/pharo-core
In a copy of the image can you try to do an image cleanup (System -> Do
image cleanup) and see if those instances still persists afterwards.
Also do you have any zombie processes? If yes can you see if killing them
releases the inspector instances.
Cheers,
Andrei
On Fri, Aug 7, 2015 at 3:00 PM,
may be related to te memory leak esteban is chasing around rubric
Le 7/8/15 15:00, teso...@gmail.com a écrit :
Hi to all,
I'm having a problem using the latest Pharo5 image.
I can use it normally, but after a time using it. I see the memory
usage has increased.
As I'm working with many
This sounds like a bug. Could you open an issue?
Cheers,
Doru
On Fri, Aug 7, 2015 at 3:00 PM, teso...@gmail.com wrote:
> Hi to all,
>I'm having a problem using the latest Pharo5 image.
>
> I can use it normally, but after a time using it. I see the memory usage
> has increased.
> As I'
Hi to all,
I'm having a problem using the latest Pharo5 image.
I can use it normally, but after a time using it. I see the memory usage
has increased.
As I'm working with many objects this usage increase very fast, each test
is creating them and discarding them.
When I started looking wher
Branch: refs/tags/50212
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: fb155151ce93d13efc3c0f1a7e53866b7f1c7ef7
https://github.com/pharo-project/pharo-core/commit/fb155151ce93d13efc3c0f1a7e53866b7f1c7ef7
Author: Jenkins Build Server
Date: 2015-08-07 (Fri, 07 Aug 2015
Le 6 août 2015 à 22:49, Dale Henrichs a écrit :
> For the Metacello tests themselves, the version of Metacello under test is
> installed on top of the version present in the image, using the "standard
> Metacello update code" ... failures at this point indicate Metacello upgrade
> problems ...
13 matches
Mail list logo
