- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo 6 crash when requesting memory from the JVM library

by Raffaello Giulietti

Unfortunately, as I just discovered, older versions of Pharo do not support UFFI. I don't have the time (nor a real interest) in backporting the code to an older pre-Spur VM which has probably reached its EOL just for the sake of experimentation. It would probably take hours to understand the older FFI model and to adapt the code for no real advantage. The current Pharo VM seems to support only the --memory option: I tried with 1 and 2 GiB, nothing changes in the misbehavior. I also tried the two heap-related JVM options in isolation, unsuccessfully. Just for information, the current values for the options are -Xms16m and -Xmx512m, meaning that the JVM heap should start with 16 MiB and grow to a maximum size of 512 MiB, both of which are rather modest values even for a 32 bit process. Besides, they work in VisualWorks (32 bit). The StackOverflow page indicated below is from year 2010, during the age of Java 6. The JVM has undergone major changes since then, including memory management, so I'm not sure the discussion there is relevant for Java 8, the release we are targeting as of today. But even if it were, I still cannot understand the crash in Pharo. On 2017-05-03 06:36, Ben Coman wrote: > > > On Wed, May 3, 2017 at 12:30 AM, Denis Kudriashov <dionisiydk(a)gmail.com > <mailto:dionisiydk@gmail.com>> wrote: > > Could you check how it works with Pharo5 which was based on prespur > CogVM? > > > Note, Pharo 5 Release was a Spur VM. > Try using... > http://files.pharo.org/get-files/50-preSpur/ > http://files.pharo.org/image/50-preSpur/50495.zip > > or even Pharo 4. > > cheers -ben > > > 2017-05-02 16:36 GMT+02:00 Raffaello Giulietti > <raffaello.giulietti(a)lifeware.ch > <mailto:raffaello.giulietti@lifeware.ch>>: > > Hello, > > I'm on Pharo 6 (32 bit)/Windows 10 (64 bit). > > I'm trying to load and use the (32 bit) JVM DLL into a running > Pharo image via the UFFI. > > Everything works correctly, including JVM method invocations, > except when trying to set the minimum and maximum JVM heap size > by passing the -Xms<size> and -Xmx<size> options upon JVM > creation. With these options, Pharo simply crashes without > leaving any trace. > > > Can you isolate whether the problem is either one of those, or it > happens with both, and if there is some cutoff where it works? Also, > perhaps try limiting heap being used by Pharo > --memory <size>[mk] use fixed heap size (added to image size) > --mmap <size>[mk] limit dynamic heap size (default: 1024m) > [out 2G on 32-bit) > --maxoldspace <size>[mk] set max size of old space memory to bytes > (disclaimer, I'm not too knowledgeable on these, just pulled them > from --help) > > Also consider that heap needs to be contiguous... > **http://stackoverflow.com/questions/2457514/understanding-max-jvm-heap-size-32bit-vs-64bit > cheers -ben > > > Apparently, memory management requests from the JVM interfere > with Pharo's own memory management. > > Please note that we successfully use the same mechanism for both > VisualWorks (32 bit)/Windows 10 (64 bit) and Gemstone 64 > bit/Linux, so it seems it has to do with a Pharo limitation somehow. > > Further, I couldn't find any documentation on how to increase > Pharo's working set. > > So the questions are: > * What is the most probable cause of the crash described above? > * Where is there more doc about Pharo's memory configuration > settings? > > Greetings > Raffaello > > > >

May 3, 2017

Re: [Pharo-dev] PI'm promoting new stable VMs

by Denis Kudriashov

Also good news that image drag and drop into latest VM works fine again 2017-05-03 10:10 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > I know, but cannot wait for promotingâ¦ is âstable enoughâ. > Alsoâ¦ problem is not present on other flavours so I guess is an image > problem. Guille worked a bit on it but we need to review some more. > > Esteban > > > On 3 May 2017, at 10:03, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi. > > Black screen on startup is still there on Mac Sierra 32 bits VM > > 2017-05-03 9:43 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> in 15min, I will promote latest VM to stable VM. >> The new stable VM has a lot of bugfixes, notably: >> >> - compactor works >> - Cairo and Surface plugin now can coexist (and it does not crashes) >> - lot of other small things >> >> cheers, >> Esteban >> >> > >

May 3, 2017

resizing the windows sometimes blocks the image

by Andrei Chis

Hi, With the latest moose image based on Pharo 6 and vm (32 bit) sometimes when I resize the main window or enter full screen mode on MacOS the window becomes totally white and does not recover:[image: Inline image 1] I need to force quit the image. Also this happens not that often and quite randomly. Does this happen to anybody else or it's just me? Cheers, Andrei

May 3, 2017

Re: [Pharo-dev] PI'm promoting new stable VMs

by Esteban Lorenzano

I know, but cannot wait for promotingâ¦ is âstable enoughâ. Alsoâ¦ problem is not present on other flavours so I guess is an image problem. Guille worked a bit on it but we need to review some more. Esteban > On 3 May 2017, at 10:03, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi. > > Black screen on startup is still there on Mac Sierra 32 bits VM > > 2017-05-03 9:43 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > in 15min, I will promote latest VM to stable VM. > The new stable VM has a lot of bugfixes, notably: > > - compactor works > - Cairo and Surface plugin now can coexist (and it does not crashes) > - lot of other small things > > cheers, > Esteban > >

May 3, 2017

Re: [Pharo-dev] PI'm promoting new stable VMs

by Denis Kudriashov

Hi. Black screen on startup is still there on Mac Sierra 32 bits VM 2017-05-03 9:43 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > in 15min, I will promote latest VM to stable VM. > The new stable VM has a lot of bugfixes, notably: > > - compactor works > - Cairo and Surface plugin now can coexist (and it does not crashes) > - lot of other small things > > cheers, > Esteban > >

May 3, 2017

PI'm promoting new stable VMs

by Esteban Lorenzano

in 15min, I will promote latest VM to stable VM. The new stable VM has a lot of bugfixes, notably: - compactor works - Cairo and Surface plugin now can coexist (and it does not crashes) - lot of other small things cheers, Esteban

May 3, 2017

[pharo-project/pharo-core]

by GitHub

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

May 3, 2017

[pharo-project/pharo-core] 6e92eb: 60478

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 6e92eb6cb6283b613727ef54630e32d3403e3f88 https://github.com/pharo-project/pharo-core/commit/6e92eb6cb6283b613727ef54… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-05-03 (Wed, 03 May 2017) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60477.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60478.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60477.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60478.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-DependencyAnalyser-Test.package/DADependencyCheckerTest.class/instance/tests/testShouldGetUnresolvedDependencies.st Log Message: ----------- 60478 19988 #testShouldGetUnresolvedDependencies can fail easily https://pharo.fogbugz.com/f/cases/19988 http://files.pharo.org/image/60/60478.zip

May 3, 2017

Re: [Pharo-dev] [Moose-dev] Re: [ann] gt4gemstone

by Mariano Martinez Peck

On Wed, May 3, 2017 at 1:55 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > > On May 3, 2017, at 1:00 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > Hi Doru, > > > > That's very cool! I am on vacation now so I don't have much time to take > a deeper look. > > Quick questions: > > 1) is this using the CGI FFI port I did for Pharo 5 UFFI? > > Of course :). > Cool! I am glad that is being used and that it was worth! I still remember the skype call we had some time ago :) > > > 2) Which pharo and gemstone versions are supported? Does this work for > Pharo 5.0 and GemStone 3.3.3 ? > > - Pharo 5.0, Pharo 6.0. > - GemStone 3.3.3 > > Excellent. That fits my client app. I will try to test it when I am back. Best, > Cheers, > Doru > > > > Thanks! > > > > > > On Tue, May 2, 2017 at 6:29 PM, Tudor Girba <tudor(a)tudorgirba.com> > wrote: > > Hi, > > > > feenk.com is proud to announce gt4gemstone, a version of the Glamorous > Toolkit aimed at supporting remote development with GemStone/S from Pharo. > gt4gemstone is released as an open-source project under the MIT license and > was built primarily by Andrei Chis with some marginal contributions from me. > > > > The project is hosted at: > > https://github.com/feenkcom/gt4gemstone > > > > The toolkit currently offers several features: > > â¢ Remote Playground > > â¢ Remote Inspector with extensions that can be coded exactly > like the ones in Pharo > > â¢ Remote Debugger with mixed stacks (Pharo and GemStone) > > â¢ Basic Remote Code Browser > > â¢ Remote Session Handler > > â¢ Integration with Roassal > > â¢ A Glamour-specific proxy model for efficient serialization of > Glamour presentations > > â¢ A basic proxy model for working with any remote objects from > GemStone > > > > One particular aspect that we focused on is performance. So much so, > that at one point inspecting objects in gt4gemstone was faster than doing > them locally. In the meantime, the GT inspector from Pharo also received an > upgrade. > > > > But, perhaps the most exciting thing about this project is that most > extensions of the inspector can be expressed exactly in the same way both > in Pharo and in GemStone, and this makes the scenario of building in Pharo > and deploying in GemStone even more appealing. > > > > The official announcement with some extra details can be found here: > > http://www.humane-assessment.com/blog/introducing-gt4gemstone/ > > > > Cheers, > > Tudor > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "There are no old things, there are only old ways of looking at them." > > > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > âLive like you mean it." > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > -- Mariano http://marianopeck.wordpress.com

May 3, 2017

Re: [Pharo-dev] [Moose-dev] [ann] gt4gemstone

by Tudor Girba

Hi, > On May 3, 2017, at 1:00 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > Hi Doru, > > That's very cool! I am on vacation now so I don't have much time to take a deeper look. > Quick questions: > 1) is this using the CGI FFI port I did for Pharo 5 UFFI? Of course :). > 2) Which pharo and gemstone versions are supported? Does this work for Pharo 5.0 and GemStone 3.3.3 ? - Pharo 5.0, Pharo 6.0. - GemStone 3.3.3 Cheers, Doru > Thanks! > > > On Tue, May 2, 2017 at 6:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > feenk.com is proud to announce gt4gemstone, a version of the Glamorous Toolkit aimed at supporting remote development with GemStone/S from Pharo. gt4gemstone is released as an open-source project under the MIT license and was built primarily by Andrei Chis with some marginal contributions from me. > > The project is hosted at: > https://github.com/feenkcom/gt4gemstone > > The toolkit currently offers several features: > â¢ Remote Playground > â¢ Remote Inspector with extensions that can be coded exactly like the ones in Pharo > â¢ Remote Debugger with mixed stacks (Pharo and GemStone) > â¢ Basic Remote Code Browser > â¢ Remote Session Handler > â¢ Integration with Roassal > â¢ A Glamour-specific proxy model for efficient serialization of Glamour presentations > â¢ A basic proxy model for working with any remote objects from GemStone > > One particular aspect that we focused on is performance. So much so, that at one point inspecting objects in gt4gemstone was faster than doing them locally. In the meantime, the GT inspector from Pharo also received an upgrade. > > But, perhaps the most exciting thing about this project is that most extensions of the inspector can be expressed exactly in the same way both in Pharo and in GemStone, and this makes the scenario of building in Pharo and deploying in GemStone even more appealing. > > The official announcement with some extra details can be found here: > http://www.humane-assessment.com/blog/introducing-gt4gemstone/ > > Cheers, > Tudor > > -- > www.tudorgirba.com > www.feenk.com > > "There are no old things, there are only old ways of looking at them." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > -- > Mariano > http://marianopeck.wordpress.com > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com âLive like you mean it."

May 3, 2017