Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

here is the correct fix: http://code.google.com/p/pharo/issues/detail?id=5005 On Wed, Jan 18, 2012 at 8:09 PM, Yanni Chiu wrote: > On 18/01/12 6:25 AM, Henrik Johansen wrote: > >> >> The real bug is that Integer>> isPowerOfTwo does not check for the edge >> case: >> > > That fixed it. #cleanUpF

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On 18/01/12 6:25 AM, Henrik Johansen wrote: The real bug is that Integer>> isPowerOfTwo does not check for the edge case: That fixed it. #cleanUpForProduction now runs to completion.

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

> > Wellit seems I found the problem. And in fact, it has alredy been > > solved by Levente in Squeak...I waste so many hours...and the fix was > > there.. > > > > So, can you try changing to > > > > sizeFor: numberOfElements > > "Return the minimum capacity of a dictionary that can hold

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On Jan 18, 2012, at 12:49 45PM, Henrik Johansen wrote: > > On Jan 18, 2012, at 12:44 58PM, Mariano Martinez Peck wrote: > >> >> >> On Wed, Jan 18, 2012 at 12:25 PM, Henrik Johansen >> wrote: >> >> On Jan 18, 2012, at 12:14 47PM, Mariano Martinez Peck wrote: >> >> > Wellit seems I foun

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On Jan 18, 2012, at 12:44 58PM, Mariano Martinez Peck wrote: > > > On Wed, Jan 18, 2012 at 12:25 PM, Henrik Johansen > wrote: > > On Jan 18, 2012, at 12:14 47PM, Mariano Martinez Peck wrote: > > > Wellit seems I found the problem. And in fact, it has alredy been > > solved by Levente i

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On Wed, Jan 18, 2012 at 12:25 PM, Henrik Johansen < henrik.s.johan...@veloxit.no> wrote: > > On Jan 18, 2012, at 12:14 47PM, Mariano Martinez Peck wrote: > > > Wellit seems I found the problem. And in fact, it has alredy been > solved by Levente in Squeak...I waste so many hours...and the fix

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On Jan 18, 2012, at 12:14 47PM, Mariano Martinez Peck wrote: > Wellit seems I found the problem. And in fact, it has alredy been solved > by Levente in Squeak...I waste so many hours...and the fix was there.. > > So, can you try changing to > > sizeFor: numberOfElements > "Return the m

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

Wellit seems I found the problem. And in fact, it has alredy been solved by Levente in Squeak...I waste so many hours...and the fix was there.. So, can you try changing to sizeFor: numberOfElements "Return the minimum capacity of a dictionary that can hold numberOfElements elements. At le

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

So is the new fix solving the problems? Stef On Jan 18, 2012, at 9:53 AM, Mariano Martinez Peck wrote: > > > On Wed, Jan 18, 2012 at 8:29 AM, Yanni Chiu wrote: > Rats, that's not the fix. > > Even though #cleanUpForRelease ran to completion, running the code: > > >Smalltalk >

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On Wed, Jan 18, 2012 at 8:30 AM, Stéphane Ducasse wrote: > Thanks. > Mariano I remember that with marcus we got the same impression: that the > copyFrom: trick to avoid > a full scan was the cause of the trouble. > But I remember that you said that you had still a problem. > I notice that the co

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On Wed, Jan 18, 2012 at 8:29 AM, Yanni Chiu wrote: > Rats, that's not the fix. > > Even though #cleanUpForRelease ran to completion, running the code: > > >Smalltalk >allClassesAndTraitsDo: [ :class | >[ :each | >each

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

Thanks. Mariano I remember that with marcus we got the same impression: that the copyFrom: trick to avoid a full scan was the cause of the trouble. But I remember that you said that you had still a problem. > Here's the fix: > > I reverted MethodDictionary>>#compact to its previous version: > >

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

Rats, that's not the fix. Even though #cleanUpForRelease ran to completion, running the code: Smalltalk allClassesAndTraitsDo: [ :class | [ :each | each removeEmptyCategories;

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

Here's the fix: I reverted MethodDictionary>>#compact to its previous version: compact "Make sure that I have the highest possible load factor (at least 50%)." self become: self compactWithoutBecome The non-working version was: compact "Make sure that I have the high

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On 17/01/12 11:14 PM, Yanni Chiu wrote: On 17/01/12 5:15 PM, Mariano Martinez Peck wrote: can you reproduce the problem with that ? Nope, the code worked in both the new and old images. Here's how I've reproduced the problem. Happens about half the time out of a handful of times - using a

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On 17/01/12 5:15 PM, Mariano Martinez Peck wrote: can you reproduce the problem with that ? Nope, the code worked in both the new and old images. At first I ran the two code snippets in two separate doIt's: "code that geenrates the bug" ... "Code to test the bug" ... Then I tried to run

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On Tue, Jan 17, 2012 at 11:13 PM, Yanni Chiu wrote: > On 17/01/12 4:44 PM, Mariano Martinez Peck wrote: > >> I have already opened an issue several months ago: >> http://code.google.com/p/**pharo/issues/detail?id=5005 >> >> I have also made it

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

On 17/01/12 4:44 PM, Mariano Martinez Peck wrote: I have already opened an issue several months ago: http://code.google.com/p/pharo/issues/detail?id=5005 I have also made it as much reproducable as I could and I have also asked for help: http://forum.world.st/Help-with-cleanUpForRelease-is-broke

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

I have already opened an issue several months ago: http://code.google.com/p/pharo/issues/detail?id=5005 I have also made it as much reproducable as I could and I have also asked for help: http://forum.world.st/Help-with-cleanUpForRelease-is-broken-MessageNotUnderstood-ByteSymbol-run-with-in-tp4205

Re: [Pharo-project] latest build yields stack trace running #cleanUpForProduction

Hi Yanni open a bug entry. We got some strange behavior with becomeForward: and set rehash and I wonder if this is not related. stef On Jan 17, 2012, at 10:03 PM, Yanni Chiu wrote: > Using Pharo 1.4 (#220), I end up in: > ByteSymbol(Object)>>doesNotUnderstand: #run:with:in: > > which was cal

[Pharo-project] latest build yields stack trace running #cleanUpForProduction

Using Pharo 1.4 (#220), I end up in: ByteSymbol(Object)>>doesNotUnderstand: #run:with:in: which was called from: (MCPackage named: self theScriptLoaderPackageName) unload. First I thought it was because I had OSProcess loaded when I ran cleanUpForProduction, and it stopped in an OSProcess c