- Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20385

by Marcus Denker

20385 ----- Issue 6936: Compiler tests dependent on TextMorph http://code.google.com/p/pharo/issues/detail?id=6936 Issue 6935: CompilerEvaluationTest dependent on Debugger http://code.google.com/p/pharo/issues/detail?id=6935 Issue 6934: move encodeForHTTP tests to own class http://code.google.com/p/pharo/issues/detail?id=6934 Issue 6918: Right click on packages over a category without MC corresponding package raises DNU http://code.google.com/p/pharo/issues/detail?id=6918 Diff information: http://ss3.gemstone.com/ss/Pharo20/NetworkTests-MarcusDenker.79.diff http://ss3.gemstone.com/ss/Pharo20/CompilerTests-MarcusDenker.127.diff http://ss3.gemstone.com/ss/Pharo20/CollectionsTests-MarcusDenker.578.diff http://ss3.gemstone.com/ss/Pharo20/CI-Core-MarcusDenker.48.diff -- Marcus Denker -- http://marcusdenker.de

Nov. 8, 2012

Re: [Pharo-project] Increase memory

by roberto.minelli＠usi.ch

Hi Fernando, On Nov 8, 2012, at 2:32 PM, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: > Ciao Roberto, which is the current size of the image? (the .image file). The image is indeed fresh, just installed FileSystemGit.. It's about 30 MB.. > If you evaluate the following a couple of times (print it cmd-p), you will cleanup most of the unreferenced objects in the image, it returns a number so you can compare it to successive evaluations. > > Smalltalk garbageCollect. > > You can also follow the pointers to objects, to detect objects which you suspect are just hanging around, and fail to be garbage collected, to clear those references. Open an inspector an any object,and the menu has that option. ( {Object. 1. #hello} inspect) . > > You can also, start with a fresh image. > > > pd: if you search the mailing list, i remember Tudor writing about large images and vm's. Then, I'll look around.. Thanks.. > > > > On Thu, Nov 8, 2012 at 2:16 PM, roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> wrote: > Hi, > > I was executing a piece of code that collects the revisions of a Git repo in Pharo but it seems Pharo requires more memory.. > > How do I increase the available memory? > > Here is the log: > > SmalltalkImage>>signalLowSpace > OutOfMemory>>defaultAction > UndefinedObject>>handleSignal: > OutOfMemory(Exception)>>pass > PasteUpMorph>>becomeActiveDuring: in Block: [:ex | ... > BlockClosure>>cull: > MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception] > BlockClosure>>ensure: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > OutOfMemory(Exception)>>signal > OutOfMemory class(Exception class)>>signal > ByteArray class(Behavior)>>basicNew: > ByteArray class(Behavior)>>new: > ByteArray(SequenceableCollection)>>copyFrom:to: > ReadStream(PositionableStream)>>contents > GitPackedNonDelta(GitPackedObject)>>compressedData > GitPackedNonDelta(GitPackedObject)>>computeCRC > GitPackedNonDelta(GitPackedObject)>>loadFrom: > GitPackedObject class>>fromPack:at:in: > GitPackFile>>objectAtOffset: > GitPackFile>>objectNamed: > GitRepository>>packedObjectNamed:ifAbsent: in Block: [:pack | (pack objectNamed: aHexHash)... > GitRepository>>packsDo: in Block: [:pack | aBlock value: pack] > OrderedCollection>>do: > GitRepository>>packsDo: > GitRepository>>packedObjectNamed:ifAbsent: > GitRepository>>objectNamed:ifAbsent: in Block: [self packedObjectNamed: aHash ifAbsent: aBlock] > GitRepository>>looseObjectNamed:ifAbsent: in Block: [^ aBlock value] > False>>ifTrue:ifFalse: > > Thanks, > Roberto >

Nov. 8, 2012

Re: [Pharo-project] New command line option: load updates

by Camillo Bruni

nice! :) now we should rewrite the monkey fully in Pharo, given that we have now almost everything needed that shouldn't be that hard anymore ;)! On 2012-11-08, at 14:39, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > There is now a command line option to load updates. > > To test it: > > wget --quiet -qO - http://pharo.gforge.inria.fr/ci/ciPharo20NBCog.sh | bash > > ./vm.sh Pharo.image update > > What is does it to load updates, then snapshot and quit. > > The idea is to use this in the new CI setup so we don't need any external scripts. > > -- > Marcus Denker -- http://marcusdenker.de > >

Nov. 8, 2012

[Pharo-project] New command line option: load updates

by Marcus Denker

Hi, There is now a command line option to load updates. To test it: wget --quiet -qO - http://pharo.gforge.inria.fr/ci/ciPharo20NBCog.sh | bash ./vm.sh Pharo.image update What is does it to load updates, then snapshot and quit. The idea is to use this in the new CI setup so we don't need any external scripts. -- Marcus Denker -- http://marcusdenker.de

Nov. 8, 2012

Re: [Pharo-project] Increase memory

by Alexandre Bergel

By passing appropriate arguments when launching the VM on the command line. Cheers, Alexandre On Nov 8, 2012, at 10:16 AM, roberto.minelli(a)usi.ch wrote: > Hi, > > I was executing a piece of code that collects the revisions of a Git repo in Pharo but it seems Pharo requires more memory.. > > How do I increase the available memory? > > Here is the log: > > SmalltalkImage>>signalLowSpace > OutOfMemory>>defaultAction > UndefinedObject>>handleSignal: > OutOfMemory(Exception)>>pass > PasteUpMorph>>becomeActiveDuring: in Block: [:ex | ... > BlockClosure>>cull: > MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception] > BlockClosure>>ensure: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > OutOfMemory(Exception)>>signal > OutOfMemory class(Exception class)>>signal > ByteArray class(Behavior)>>basicNew: > ByteArray class(Behavior)>>new: > ByteArray(SequenceableCollection)>>copyFrom:to: > ReadStream(PositionableStream)>>contents > GitPackedNonDelta(GitPackedObject)>>compressedData > GitPackedNonDelta(GitPackedObject)>>computeCRC > GitPackedNonDelta(GitPackedObject)>>loadFrom: > GitPackedObject class>>fromPack:at:in: > GitPackFile>>objectAtOffset: > GitPackFile>>objectNamed: > GitRepository>>packedObjectNamed:ifAbsent: in Block: [:pack | (pack objectNamed: aHexHash)... > GitRepository>>packsDo: in Block: [:pack | aBlock value: pack] > OrderedCollection>>do: > GitRepository>>packsDo: > GitRepository>>packedObjectNamed:ifAbsent: > GitRepository>>objectNamed:ifAbsent: in Block: [self packedObjectNamed: aHash ifAbsent: aBlock] > GitRepository>>looseObjectNamed:ifAbsent: in Block: [^ aBlock value] > False>>ifTrue:ifFalse: > > Thanks, > Roberto -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 8, 2012

Re: [Pharo-project] Increase memory

by Fernando Olivero

Ciao Roberto, which is the current size of the image? (the .image file). If you evaluate the following a couple of times (print it cmd-p), you will cleanup most of the unreferenced objects in the image, it returns a number so you can compare it to successive evaluations. Smalltalk garbageCollect. You can also follow the pointers to objects, to detect objects which you suspect are just hanging around, and fail to be garbage collected, to clear those references. Open an inspector an any object,and the menu has that option. ( {Object. 1. #hello} inspect) . You can also, start with a fresh image. pd: if you search the mailing list, i remember Tudor writing about large images and vm's. On Thu, Nov 8, 2012 at 2:16 PM, roberto.minelli(a)usi.ch < roberto.minelli(a)usi.ch> wrote: > Hi, > > I was executing a piece of code that collects the revisions of a Git repo > in Pharo but it seems Pharo requires more memory.. > > How do I increase the available memory? > > Here is the log: > > SmalltalkImage>>signalLowSpace > OutOfMemory>>defaultAction > UndefinedObject>>handleSignal: > OutOfMemory(Exception)>>pass > PasteUpMorph>>becomeActiveDuring: in Block: [:ex | ... > BlockClosure>>cull: > MethodContext(ContextPart)>>handleSignal: in Block: [self > exceptionHandlerBlock cull: exception] > BlockClosure>>ensure: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > OutOfMemory(Exception)>>signal > OutOfMemory class(Exception class)>>signal > ByteArray class(Behavior)>>basicNew: > ByteArray class(Behavior)>>new: > ByteArray(SequenceableCollection)>>copyFrom:to: > ReadStream(PositionableStream)>>contents > GitPackedNonDelta(GitPackedObject)>>compressedData > GitPackedNonDelta(GitPackedObject)>>computeCRC > GitPackedNonDelta(GitPackedObject)>>loadFrom: > GitPackedObject class>>fromPack:at:in: > GitPackFile>>objectAtOffset: > GitPackFile>>objectNamed: > GitRepository>>packedObjectNamed:ifAbsent: in Block: [:pack | (pack > objectNamed: aHexHash)... > GitRepository>>packsDo: in Block: [:pack | aBlock value: pack] > OrderedCollection>>do: > GitRepository>>packsDo: > GitRepository>>packedObjectNamed:ifAbsent: > GitRepository>>objectNamed:ifAbsent: in Block: [self packedObjectNamed: > aHash ifAbsent: aBlock] > GitRepository>>looseObjectNamed:ifAbsent: in Block: [^ aBlock value] > False>>ifTrue:ifFalse: > > Thanks, > Roberto >

Nov. 8, 2012

[Pharo-project] Increase memory

by roberto.minelli＠usi.ch

Hi, I was executing a piece of code that collects the revisions of a Git repo in Pharo but it seems Pharo requires more memory.. How do I increase the available memory? Here is the log: SmalltalkImage>>signalLowSpace OutOfMemory>>defaultAction UndefinedObject>>handleSignal: OutOfMemory(Exception)>>pass PasteUpMorph>>becomeActiveDuring: in Block: [:ex | ... BlockClosure>>cull: MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception] BlockClosure>>ensure: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: OutOfMemory(Exception)>>signal OutOfMemory class(Exception class)>>signal ByteArray class(Behavior)>>basicNew: ByteArray class(Behavior)>>new: ByteArray(SequenceableCollection)>>copyFrom:to: ReadStream(PositionableStream)>>contents GitPackedNonDelta(GitPackedObject)>>compressedData GitPackedNonDelta(GitPackedObject)>>computeCRC GitPackedNonDelta(GitPackedObject)>>loadFrom: GitPackedObject class>>fromPack:at:in: GitPackFile>>objectAtOffset: GitPackFile>>objectNamed: GitRepository>>packedObjectNamed:ifAbsent: in Block: [:pack | (pack objectNamed: aHexHash)... GitRepository>>packsDo: in Block: [:pack | aBlock value: pack] OrderedCollection>>do: GitRepository>>packsDo: GitRepository>>packedObjectNamed:ifAbsent: GitRepository>>objectNamed:ifAbsent: in Block: [self packedObjectNamed: aHash ifAbsent: aBlock] GitRepository>>looseObjectNamed:ifAbsent: in Block: [^ aBlock value] False>>ifTrue:ifFalse: Thanks, Roberto

Nov. 8, 2012

Re: [Pharo-project] NB integration

by Esteban Lorenzano

yes... but the athens ready VMs are also coming with pharo 2.0 so... On Nov 8, 2012, at 4:29 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 2 November 2012 10:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> pharo 2.0 will be "athens ready"... that means NB ready too :) >> > well, i actually thought that we ship "athens-ready" VMs first.. > > But as long as we want to put an Athens preview into image.. that will > also mean having NB loaded into image. > > (hearing chords of 'unnecessary bloating base image size' from afar) :) > > eh.. everything has its cost. > >> On Nov 2, 2012, at 2:00 PM, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: >> >> >> you got my vote if it is easy enough to do ;) >> >> ________________________________ >> From: Torsten Bergmann <astares(a)gmx.de> >> To: pharo-project(a)lists.gforge.inria.fr >> Sent: Friday, 2 November 2012, 12:15 >> Subject: [Pharo-project] NB integration >> >> AFAIK there was a plan to integrate NativeBoost >> into Pharo. Is it for 2.0 or 2.1? >> >> I would like to see it for 2.0... >> >> Thx >> T. >> >> >> >> > > > > -- > Best regards, > Igor Stasenko. >

Nov. 8, 2012

Re: [Pharo-project] Replace ByteArray with a smaller one

by Mariano Martinez Peck

On Thu, Nov 8, 2012 at 4:24 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 7 November 2012 11:11, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> if the chunks you wan to cut off are big enough you could >> potentially allocate a new object there which get's gc-ed. >> > yes.. > actually you can 'crop' the existing object by modifying its size > field (so VM will know it) > and then for the rest bytes, mark them as a 'free chunk', which designates a > unused memory space in heap. > actually, this could be a good candidate for a primitive. Exactlly. I was hoping there was already a primitive for that :( > But imo, much better strategy is to not allocate too big arrays. :) > > Also, as alternative , you can create a 'ArraySlice' collection class, > which is a view on existing array but with smaller number or elements. > And pass it around as a valid collection. > >> But I have no clue how to do that without VM / NB support ;) >> :( >> >> On 2012-11-07, at 14:39, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> >>> Hi guys. I have a ByteArray of size N. >>> And I want now only the same ByteArray but from 1 to N-X. I am using >>> #copyFrom:to: but that one answers a new copy. If the ByteArray is large, >>> this takes time because it needs to allocate a large object. In my case I >>> don't care and I can modify the original ByteArray itself (lets say make it >>> smaller, null the remaining part and change the object header info). That >>> way I would avoid an extra allocation. Is there a primitive for that? >>> >>> Thanks! >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >> >> > > > > -- > Best regards, > Igor Stasenko. > -- Mariano http://marianopeck.wordpress.com

Nov. 8, 2012

Re: [Pharo-project] PluggableListMorph error, how to debug ?

by Henrik Sperre Johansen

On 04.11.2012 18:37, Benjamin wrote: > In Pharo 1.4, browse Morph > Find the method fullDrawOn: > > and replace > > on: Error do: [:err | > self setProperty: #errorOnDraw toValue: true. > self setProperty: #drawError toValue: err freeze. > ^ self drawErrorOn: aCanvas > ] > > by: > value > > Now you will have a debugger instead of the red square of death > > But do it at you own risk ^^ > Ben > Debugging UI code is one of those places you probably want to insert a haltOnce instead, or risk losing the image :) Cheers, Henry

Nov. 8, 2012