November 2014 - Pharo-dev - lists.pharo.org

Reproducible VM crash with excessive garbage collection

by Max Leske

Hi. I may have discovered a bug in the PharoVM (stable and latest), which may have been around for at least two years (I had a very similiar situation about two years ago with Fuel). I have a test that fails when a particular method contains â3 timesRepeat: [ Smalltalk garbageCollect ]â. In order to be sure that itâ not the #timesRepeat message thatâs causing the crash, I replaced that with multiple âSmalltalk garbageCollectâ sends. The test Iâm talking about ObsoleteTest>>testFixObsoleteSharedPools. To make the test crash the VM, simply add a couple of garbageCollects at the end of SmalltalkImage>>fixObsoleteSharedPools. I tried to come up with a little script to demonstrate the issue but I can only reproduce the problem with Nautilus (which makes me suspect that the problem is related to Nautilus). Steps to reproduce: 1. get a fresh image and the latest vm: curl get.pharo.org/40+vmLastest <http://get.pharo.org/40+vmLastest> | bash && ./pharo-ui Pharo.image 2. open the class browser and navigate to SmalltalkImage>>fixObsoleteSharedPools 3. Append ten âself garbageCollectâ statements to the method. 4. navigate to ObsoleteTest>>testFixObsoleteSharedPools and click on the test runner icon to the left of the method name. I can reproduce this with the Mac VM (OS X 10.10) as well as with the linux VM (Ubuntu 12.04.1). Iâve opened an issue for this: https://pharo.fogbugz.com/f/cases/14478/Reproducible-VM-crash-with-excessiv… <https://pharo.fogbugz.com/f/cases/14478/Reproducible-VM-crash-with-excessiv…> Cheers, Max

Nov. 16, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 0635d1: 40371

by Ben Coman

Marcus Denker wrote: > >> On 16 Nov 2014, at 16:47, Marcus Denker <marcus.denker(a)inria.fr >> <mailto:marcus.denker@inria.fr>> wrote: >> >>> >>> On 16 Nov 2014, at 16:31, Marcus Denker <marcus.denker(a)inria.fr >>> <mailto:marcus.denker@inria.fr>> wrote: >>> >>> >>>>> Log Message: >>>>> ----------- >>>>> 40371 >>>>> 14261 Delay refactoring (part 1) - move scheduler from class-side >>>>> to instance-side of its own class >>>>> https://pharo.fogbugz.com/f/cases/14261 >>>>> http://files.pharo.org/image/40/40371.zip >>>> >>>> Thanks very much for that, but it picked up the .4 slice >>>> rather than the .9 slice. Probably due to my changing the issue >>>> title half way through (sorry). >>>> >>> Ok, I will do a manual integration of .9.. good that it does not need >>> a roll-back. >>> >> >> The result is that two tests are failing now in 372: >> >> KernelTests.Processes.SemaphoreTest.testWaitAndWaitTimeoutTogether >> KernelTests.Processes.SemaphoreTest.testWaitTimeoutMSecs >> > > And the step 3 is failing. > > https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-3-Minimal/223/ > > I give up for today. > > I think we should revert both 372 and 371â¦ but I will not do that today > as this is sunday. > (lesson learned: never ingrate if you canât spend 3 hoursâ¦) > > Marcus I can confirm those failing tests, in both slice.4 and slice.9, so strange they didn't chow up in the Validator report. Now if its less work, you can revert to the original code by doing "Delay newCodeEnabled: false", and both tests will pass. It late here, so I'll work on fixing those tests tomorrow. Thanks for your efforts. cheers -ben

Nov. 16, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 0635d1: 40371

by Marcus Denker

> On 16 Nov 2014, at 16:47, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 16 Nov 2014, at 16:31, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>>> Log Message: >>>> ----------- >>>> 40371 >>>> 14261 Delay refactoring (part 1) - move scheduler from class-side to instance-side of its own class >>>> https://pharo.fogbugz.com/f/cases/14261 >>>> http://files.pharo.org/image/40/40371.zip >>> >>> Thanks very much for that, but it picked up the .4 slice >>> rather than the .9 slice. Probably due to my changing the issue title half way through (sorry). >>> >> Ok, I will do a manual integration of .9.. good that it does not need a roll-back. >> > > The result is that two tests are failing now in 372: > > KernelTests.Processes.SemaphoreTest.testWaitAndWaitTimeoutTogether > KernelTests.Processes.SemaphoreTest.testWaitTimeoutMSecs > And the step 3 is failing. https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-3-Minimal/223/ I give up for today. I think we should revert both 372 and 371â¦ but I will not do that today as this is sunday. (lesson learned: never ingrate if you canât spend 3 hoursâ¦) Marcus

Nov. 16, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 0635d1: 40371

by Marcus Denker

> On 16 Nov 2014, at 16:31, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >>> Log Message: >>> ----------- >>> 40371 >>> 14261 Delay refactoring (part 1) - move scheduler from class-side to instance-side of its own class >>> https://pharo.fogbugz.com/f/cases/14261 >>> http://files.pharo.org/image/40/40371.zip >> >> Thanks very much for that, but it picked up the .4 slice >> rather than the .9 slice. Probably due to my changing the issue title half way through (sorry). >> > Ok, I will do a manual integration of .9.. good that it does not need a roll-back. > The result is that two tests are failing now in 372: KernelTests.Processes.SemaphoreTest.testWaitAndWaitTimeoutTogether KernelTests.Processes.SemaphoreTest.testWaitTimeoutMSecs Marcus

Nov. 16, 2014

Re: [Pharo-dev] [smalltalk-research] Re: Julia vs Pharo

by Serge Stinckwich

On Sun, Nov 16, 2014 at 1:45 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Serge! > > Thanks for sharing this. > > I indeed believe that scientific computing will play a big role in Pharo adoption by a large public The problem is that you need to invest at least 5 years of work before having some impact in this domain. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Help fight Ebola by joining the Computing for Ebola Challenge http://bit.ly/1oEdBag

Nov. 16, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 0635d1: 40371

by Marcus Denker

>> Log Message: >> ----------- >> 40371 >> 14261 Delay refactoring (part 1) - move scheduler from class-side to instance-side of its own class >> https://pharo.fogbugz.com/f/cases/14261 >> http://files.pharo.org/image/40/40371.zip > > Thanks very much for that, but it picked up the .4 slice > rather than the .9 slice. Probably due to my changing the issue title half way through (sorry). > Ok, I will do a manual integration of .9.. good that it does not need a roll-back. Marcus

Nov. 16, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 0635d1: 40371

by Ben Coman

GitHub wrote: > Branch: refs/heads/4.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 0635d15a291debc0717b5f2711d3832e1a77f2e6 > https://github.com/pharo-project/pharo-core/commit/0635d15a291debc0717b5f27… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2014-11-16 (Sun, 16 Nov 2014) > > Changed paths: > M Kernel.package/Delay.class/README.md > M Kernel.package/Delay.class/class/class initialization/initialize.st > A Kernel.package/Delay.class/class/enable new code/newCodeEnabled.st > A Kernel.package/Delay.class/class/enable new code/newCodeEnabled_.st > M Kernel.package/Delay.class/class/snapshotting/restoreResumptionTimes.st > M Kernel.package/Delay.class/class/snapshotting/saveResumptionTimes.st > M Kernel.package/Delay.class/class/snapshotting/shutDown.st > M Kernel.package/Delay.class/class/snapshotting/startUp.st > M Kernel.package/Delay.class/class/testing/anyActive.st > M Kernel.package/Delay.class/class/testing/nextWakeUpTime.st > M Kernel.package/Delay.class/class/timer process/handleTimerEvent.st > M Kernel.package/Delay.class/class/timer process/runTimerEventLoop.st > M Kernel.package/Delay.class/class/timer process/scheduleDelay_.st > M Kernel.package/Delay.class/class/timer process/schedulingProcess.st > M Kernel.package/Delay.class/class/timer process/startTimerEventLoop.st > A Kernel.package/Delay.class/class/timer process/startTimerEventLoop_.st > M Kernel.package/Delay.class/class/timer process/stopTimerEventLoop.st > M Kernel.package/Delay.class/class/timer process/unscheduleDelay_.st > M Kernel.package/Delay.class/definition.st > A Kernel.package/Delay.class/instance/enable new code/newCodeEnabled.st > M Kernel.package/Delay.class/instance/private/schedule.st > M Kernel.package/Delay.class/instance/private/unschedule.st > A Kernel.package/DelayScheduler.class/README.md > A Kernel.package/DelayScheduler.class/definition.st > A Kernel.package/DelayScheduler.class/instance/class initialization/initialize.st > A Kernel.package/DelayScheduler.class/instance/low priority processes/schedule_.st > A Kernel.package/DelayScheduler.class/instance/low priority processes/unschedule_.st > A Kernel.package/DelayScheduler.class/instance/primitives/primSignal_atMilliseconds_.st > A Kernel.package/DelayScheduler.class/instance/snapshotting/restoreResumptionTimes.st > A Kernel.package/DelayScheduler.class/instance/snapshotting/saveResumptionTimes.st > A Kernel.package/DelayScheduler.class/instance/snapshotting/shutDown.st > A Kernel.package/DelayScheduler.class/instance/snapshotting/startUp.st > A Kernel.package/DelayScheduler.class/instance/testing/anyActive.st > A Kernel.package/DelayScheduler.class/instance/testing/nextWakeUpTime.st > A Kernel.package/DelayScheduler.class/instance/timer process/handleTimerEvent_.st > A Kernel.package/DelayScheduler.class/instance/timer process/runTimerEventLoop.st > A Kernel.package/DelayScheduler.class/instance/timer process/scheduleDelay_.st > A Kernel.package/DelayScheduler.class/instance/timer process/schedulingProcess.st > A Kernel.package/DelayScheduler.class/instance/timer process/startTimerEventLoop.st > A Kernel.package/DelayScheduler.class/instance/timer process/startTimerEventLoop_.st > A Kernel.package/DelayScheduler.class/instance/timer process/stopTimerEventLoop.st > A Kernel.package/DelayScheduler.class/instance/timer process/unscheduleDelay_.st > A KernelTests.package/DelayBenchmark.class/README.md > A KernelTests.package/DelayBenchmark.class/class/action/run.st > A KernelTests.package/DelayBenchmark.class/definition.st > A KernelTests.package/DelayBenchmark.class/instance/action/run.st > A KernelTests.package/DelayBenchmark.class/instance/support/generateDelayProcesses_priority_maxDuration_fromSeed_.st > A KernelTests.package/DelayBenchmark.class/instance/support/trialConcurrent_priority_maxDuration_fromSeed_.st > A KernelTests.package/DelaySchedulerTest.class/README.md > A KernelTests.package/DelaySchedulerTest.class/definition.st > A KernelTests.package/DelaySchedulerTest.class/instance/tests/testMaxTickLessThanDuration.st > A KernelTests.package/DelaySchedulerTest.class/instance/tests/testMaxTickMoreThanDuration.st > A KernelTests.package/extension/DelayScheduler/instance/testCaseSupportActiveDelay.st > A KernelTests.package/extension/DelayScheduler/instance/testCaseSupportSetActiveDelayStartTime_.st > A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script371.st > A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40371.st > M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > > Log Message: > ----------- > 40371 > 14261 Delay refactoring (part 1) - move scheduler from class-side to instance-side of its own class > https://pharo.fogbugz.com/f/cases/14261 > > http://files.pharo.org/image/40/40371.zip > > Thanks very much for that, but it picked up the .4 slice rather than the .9 slice. Probably due to my changing the issue title half way through (sorry). -ben

Nov. 16, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40371 Home: https://github.com/pharo-project/pharo-core

Nov. 16, 2014

[pharo-project/pharo-core] 0635d1: 40371

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 0635d15a291debc0717b5f2711d3832e1a77f2e6 https://github.com/pharo-project/pharo-core/commit/0635d15a291debc0717b5f27… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-16 (Sun, 16 Nov 2014) Changed paths: M Kernel.package/Delay.class/README.md M Kernel.package/Delay.class/class/class initialization/initialize.st A Kernel.package/Delay.class/class/enable new code/newCodeEnabled.st A Kernel.package/Delay.class/class/enable new code/newCodeEnabled_.st M Kernel.package/Delay.class/class/snapshotting/restoreResumptionTimes.st M Kernel.package/Delay.class/class/snapshotting/saveResumptionTimes.st M Kernel.package/Delay.class/class/snapshotting/shutDown.st M Kernel.package/Delay.class/class/snapshotting/startUp.st M Kernel.package/Delay.class/class/testing/anyActive.st M Kernel.package/Delay.class/class/testing/nextWakeUpTime.st M Kernel.package/Delay.class/class/timer process/handleTimerEvent.st M Kernel.package/Delay.class/class/timer process/runTimerEventLoop.st M Kernel.package/Delay.class/class/timer process/scheduleDelay_.st M Kernel.package/Delay.class/class/timer process/schedulingProcess.st M Kernel.package/Delay.class/class/timer process/startTimerEventLoop.st A Kernel.package/Delay.class/class/timer process/startTimerEventLoop_.st M Kernel.package/Delay.class/class/timer process/stopTimerEventLoop.st M Kernel.package/Delay.class/class/timer process/unscheduleDelay_.st M Kernel.package/Delay.class/definition.st A Kernel.package/Delay.class/instance/enable new code/newCodeEnabled.st M Kernel.package/Delay.class/instance/private/schedule.st M Kernel.package/Delay.class/instance/private/unschedule.st A Kernel.package/DelayScheduler.class/README.md A Kernel.package/DelayScheduler.class/definition.st A Kernel.package/DelayScheduler.class/instance/class initialization/initialize.st A Kernel.package/DelayScheduler.class/instance/low priority processes/schedule_.st A Kernel.package/DelayScheduler.class/instance/low priority processes/unschedule_.st A Kernel.package/DelayScheduler.class/instance/primitives/primSignal_atMilliseconds_.st A Kernel.package/DelayScheduler.class/instance/snapshotting/restoreResumptionTimes.st A Kernel.package/DelayScheduler.class/instance/snapshotting/saveResumptionTimes.st A Kernel.package/DelayScheduler.class/instance/snapshotting/shutDown.st A Kernel.package/DelayScheduler.class/instance/snapshotting/startUp.st A Kernel.package/DelayScheduler.class/instance/testing/anyActive.st A Kernel.package/DelayScheduler.class/instance/testing/nextWakeUpTime.st A Kernel.package/DelayScheduler.class/instance/timer process/handleTimerEvent_.st A Kernel.package/DelayScheduler.class/instance/timer process/runTimerEventLoop.st A Kernel.package/DelayScheduler.class/instance/timer process/scheduleDelay_.st A Kernel.package/DelayScheduler.class/instance/timer process/schedulingProcess.st A Kernel.package/DelayScheduler.class/instance/timer process/startTimerEventLoop.st A Kernel.package/DelayScheduler.class/instance/timer process/startTimerEventLoop_.st A Kernel.package/DelayScheduler.class/instance/timer process/stopTimerEventLoop.st A Kernel.package/DelayScheduler.class/instance/timer process/unscheduleDelay_.st A KernelTests.package/DelayBenchmark.class/README.md A KernelTests.package/DelayBenchmark.class/class/action/run.st A KernelTests.package/DelayBenchmark.class/definition.st A KernelTests.package/DelayBenchmark.class/instance/action/run.st A KernelTests.package/DelayBenchmark.class/instance/support/generateDelayProcesses_priority_maxDuration_fromSeed_.st A KernelTests.package/DelayBenchmark.class/instance/support/trialConcurrent_priority_maxDuration_fromSeed_.st A KernelTests.package/DelaySchedulerTest.class/README.md A KernelTests.package/DelaySchedulerTest.class/definition.st A KernelTests.package/DelaySchedulerTest.class/instance/tests/testMaxTickLessThanDuration.st A KernelTests.package/DelaySchedulerTest.class/instance/tests/testMaxTickMoreThanDuration.st A KernelTests.package/extension/DelayScheduler/instance/testCaseSupportActiveDelay.st A KernelTests.package/extension/DelayScheduler/instance/testCaseSupportSetActiveDelayStartTime_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script371.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40371.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40371 14261 Delay refactoring (part 1) - move scheduler from class-side to instance-side of its own class https://pharo.fogbugz.com/f/cases/14261 http://files.pharo.org/image/40/40371.zip

Nov. 16, 2014

Re: [Pharo-dev] How to add a morph to a Spec GUI

by kilon alios

thanks for the info Nicolai, what I am trying to do is super simple, as you can see from the code I linked I have a very simple interface of a single button, I want to put before that button a simple morph to display color. Basically the button changes the background color of windows and I want the morph to display the color. Morph wise i can create the Morph like this backgroundColorMorph := Morph new. backgroundColorMorph color: self backgroundColor. the problem is how I add this Morph to my gui. Meaning how to wrap it as spec widget which is what your code is doing. I was not aware of asSpecAdapter. Documentation does not mention this in Pharo for the Enterprise Spec Chapter. So following your instructions i added to my initialise method backgroundColorMorph := Morph new. backgroundColorWidget := backgroundColorMorph asSpecAdapter . I added a method to return backgroundColorWidget with the same name and changed at class side defaultSpec to defaultSpec <spec> ^ SpecLayout composed newRow: [:r | r add: #button width: 25. r add: #backgroundColorWidget] ; yourself I try to open the Spec gui and gives me a MNU Morph>>layout: Am I suppose to add some form of layout to the morph ? Do I need to add something to initialiseWidgets ? On Sun, Nov 16, 2014 at 12:36 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > 2014-11-16 10:02 GMT+01:00 kilon alios <kilon.alios(a)gmail.com>: > >> Hello guys I am trying to add a morph to spec gui before a spec button >> and the experience has been a nightmare so far. >> >> >> https://github.com/kilon/Nireas/blob/master/Nireas.package/Nireas.class/cla… >> > > What do you mean "add a morph to spec gui". The common way is to define > your own model and instead of composing > your GUI with different morphs, you compose your GUI with different > (ready-made) models. If you need a new > kind of 1 model-GUI-Widget you'll have to define your own spec > (morphic)adapter and add a spec binding. > > If you just want to add an existing morph into your layout, you can use > Morphic>>#asSpecAdapter. > > This example looks a bit ugly, just because it uses a > DynamicComposableModel. In your own > applicatoin you would define your own model for defining and composing the > parts: > > > class:=AthensFlakeDemo. > method:=AthensFlakeDemo>>#initialize. > composed:= DynamicComposableModel new. > composed instantiateModels: #(code TextModel method TextInputFieldModel). > > "this is a hack, as #instantiateModels: does not work for non-spec-models" > composed widgets at:#demo put:(AthensFlakeDemo new asSpecAdapter). > > "with your own model (instead of using DynamicComposableModel) you would" > "define a method that returns the morph asSpecadapter " > > composed code text:method sourceCode. > composed method text: method selector asString. > composed code aboutToStyle:true. > composed code behavior:class. > composed title:(class asString). > composed openWithSpecLayout:( > SpecLayout composed > newColumn:[:r | r > add: #demo height:80; > add: #method height:25; > add: #code]; > yourself). > > > > > > > >> >> I understand how columns and rows work but I cant figure out how Spec >> works with Morphs. >> >> I took a look at CheckBoxExample but it completely jammed my brain how >> complex it looks. >> >> First of all defaultSpec2 is what ? and whats the diffirence with >> defaultSpec ? >> >> Dont know about you but I don't like neither name defaultSpec and >> defaultSpec2 , I would have chosen a name like layout or something that >> makes sense. >> >> also why we need to initializeWidgets when we already define their order >> in defaultSpec ? Why cant Spec initialise those widgets by itself ? >> >> Is it really necessary for each element of the gui to be defined as a >> getter method ? Why not just put everything to a dictionary and make a >> getter for that dictionary ? It would make a complex Spec gui a nightmare >> to browser and leads to braking it up to more classes which will still make >> it a mess to browse. >> >> I see also a container defined in there , I assume it has something to >> do with the morphs. >> >> I took also a look at documentation at Pharo for the Enterprise and it >> has a section for building widgets but it looks too much work to add just a >> few morph to a Spec gui. >> >> I wanted to make the gui for Nireas with Spec and I like some of its >> design but overall it has been way more struggle than working with Morphic. >> >> I know I have complained about Spec before and sorry if I sound like a >> broken tape but making guis in heavily gui based environment like Pharo >> should not be so hard. >> >> I dont have a problem failing back to Morphic but since I see so many >> people praise Spec I keep wondering if I approach this the wrong way and >> things are much more elegant and easy than they look. >> > >

Nov. 16, 2014