- Pharo-dev - lists.pharo.org

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

by Eliot Miranda

Hi Ben, > On May 16, 2017, at 7:42 AM, Ben Coman <btc(a)openinworld.com> wrote: > > On Tue, May 2, 2017 at 10:36 PM, Raffaello Giulietti > <raffaello.giulietti(a)lifeware.ch> wrote: >> 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. >> >> 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? > > I just bumped into this which you may find interesting... > https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/platforms/unix/v… > * The upshot of all this is that Squeak will claim (and hold on to) > * ALL of the available virtual memory (or at least 75% of it) when > * it starts up. If you can't live with that, use the -memory > * option to allocate a fixed size heap. Please be careful to read the code. This is the situation on *non-Spur* VMs (Pharo 5 and earlier, Squeak 4.x and earlier). It is *not* the case on Spur. In Spur on start up the VM allocates enough memory for the heap plus one "growth increment" (currently 16mb) and new space (current default about 5mb on 32 bits, 9mb on 64 bits), and for the native code zone (1mb on x86, about 1.4mb on arm and x64). Spur *does not* reserve address space for the heap. It requests memory for the heap in segments (default 16mb; controllable via a vmParameterAt:put: send). It returns those segments to the is when GC frees segments (the threshold being controllable via a vmParameterAt:put: send). > > cheers -ben >

May 16, 2017

Re: [Pharo-dev] [Vm-dev] Is there a way to know if I am in iTimer VM?

by Tobias Pape

[sorry that was meant for vm-dev :(] > On 16.05.2017, at 17:20, Tobias Pape <Das.Linux(a)gmx.de> wrote: > > >> On 16.05.2017, at 17:14, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi Mariano, >> >> On May 16, 2017, at 7:48 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> >>> >>> >>> On Tue, May 16, 2017 at 11:43 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>> >>> Hi Mariano, >>> >>> On May 16, 2017, at 6:35 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >>> >>>> Guys, >>>> >>>> As you know, OSSubprocess does not work correctly in Linux unless you use the iTimer VM. >>> >>> As others have pointed out, you mean that OSSubprocess does not work correctly unless you use the threaded heartbeat VM. That the itinerary heartbeat breaks OSSubprocess. >>> >>> >>> Yes, sorry about that. >>> >>> >>>> I would like to open a warning (that growl thingy on bottom left of the screen) or something at loading / install time if I can detect I am under Linux AND under traditional linux VM (not itimer). >>>> >>>> Do you know how can I do that? >>> I made a mistake in that there is no way, other than by using the FFI, to discover if the timer heartbeat is being used. Would it be satisfactory if I provide a flag in vm parameter 48 that, if set, indicates the itimer heartbeat is in use? This could be done in a few minutes and would be ready for the official release of Pharo 6. >>>> >>> >>> Well, it would be helpful as I may be able to throw a warning. Would this flag be set only under Linux VM? >> >> Effectively, yes. It would be set in VMs that use the itimer heartbeat. Currently that's only a subset of the Linux VMs. Hopefully it will not be set in any vm soon :-) > > > Can't guarantee that to you. > Not unless the threaded-heartbeat-vm can be used hazzle-free (ie, without using sudo/..) ;) > > SCNR, sorrry > >> >>> >>> Thanks, >>> >>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >

May 16, 2017

Re: [Pharo-dev] [Vm-dev] Is there a way to know if I am in iTimer VM?

by Tobias Pape

> On 16.05.2017, at 17:14, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Mariano, > > On May 16, 2017, at 7:48 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > >> >> >> On Tue, May 16, 2017 at 11:43 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi Mariano, >> >> On May 16, 2017, at 6:35 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> >>> Guys, >>> >>> As you know, OSSubprocess does not work correctly in Linux unless you use the iTimer VM. >> >> As others have pointed out, you mean that OSSubprocess does not work correctly unless you use the threaded heartbeat VM. That the itinerary heartbeat breaks OSSubprocess. >> >> >> Yes, sorry about that. >> >> >>> I would like to open a warning (that growl thingy on bottom left of the screen) or something at loading / install time if I can detect I am under Linux AND under traditional linux VM (not itimer). >>> >>> Do you know how can I do that? >> I made a mistake in that there is no way, other than by using the FFI, to discover if the timer heartbeat is being used. Would it be satisfactory if I provide a flag in vm parameter 48 that, if set, indicates the itimer heartbeat is in use? This could be done in a few minutes and would be ready for the official release of Pharo 6. >>> >> >> Well, it would be helpful as I may be able to throw a warning. Would this flag be set only under Linux VM? > > Effectively, yes. It would be set in VMs that use the itimer heartbeat. Currently that's only a subset of the Linux VMs. Hopefully it will not be set in any vm soon :-) Can't guarantee that to you. Not unless the threaded-heartbeat-vm can be used hazzle-free (ie, without using sudo/..) ;) SCNR, sorrry > >> >> Thanks, >> >> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com

May 16, 2017

Re: [Pharo-dev] [Vm-dev] Is there a way to know if I am in iTimer VM?

by Eliot Miranda

Hi Mariano, > On May 16, 2017, at 7:48 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > >> On Tue, May 16, 2017 at 11:43 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi Mariano, >> >>> On May 16, 2017, at 6:35 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >>> >>> Guys, >>> >>> As you know, OSSubprocess does not work correctly in Linux unless you use the iTimer VM. >> >> As others have pointed out, you mean that OSSubprocess does not work correctly unless you use the threaded heartbeat VM. That the itinerary heartbeat breaks OSSubprocess. > > > Yes, sorry about that. > >> >>> I would like to open a warning (that growl thingy on bottom left of the screen) or something at loading / install time if I can detect I am under Linux AND under traditional linux VM (not itimer). >>> >>> Do you know how can I do that? >> I made a mistake in that there is no way, other than by using the FFI, to discover if the timer heartbeat is being used. Would it be satisfactory if I provide a flag in vm parameter 48 that, if set, indicates the itimer heartbeat is in use? This could be done in a few minutes and would be ready for the official release of Pharo 6. >>> > > Well, it would be helpful as I may be able to throw a warning. Would this flag be set only under Linux VM? Effectively, yes. It would be set in VMs that use the itimer heartbeat. Currently that's only a subset of the Linux VMs. Hopefully it will not be set in any vm soon :-) > > Thanks, > > >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >> > > > > -- > Mariano > http://marianopeck.wordpress.com

May 16, 2017

Re: [Pharo-dev] [Vm-dev] Is there a way to know if I am in iTimer VM?

by Mariano Martinez Peck

On Tue, May 16, 2017 at 11:43 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Mariano, > > On May 16, 2017, at 6:35 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > Guys, > > As you know, OSSubprocess does not work correctly in Linux unless you use > the iTimer VM. > > > As others have pointed out, you mean that OSSubprocess does not work > correctly unless you use the threaded heartbeat VM. That the itinerary > heartbeat breaks OSSubprocess. > Yes, sorry about that. > > I would like to open a warning (that growl thingy on bottom left of the > screen) or something at loading / install time if I can detect I am under > Linux AND under traditional linux VM (not itimer). > > Do you know how can I do that? > > I made a mistake in that there is no way, other than by using the FFI, to > discover if the timer heartbeat is being used. Would it be satisfactory if > I provide a flag in vm parameter 48 that, if set, indicates the itimer > heartbeat is in use? This could be done in a few minutes and would be > ready for the official release of Pharo 6. > > > Well, it would be helpful as I may be able to throw a warning. Would this flag be set only under Linux VM? Thanks, > -- > Mariano > http://marianopeck.wordpress.com > > > -- Mariano http://marianopeck.wordpress.com

May 16, 2017

Re: [Pharo-dev] Is there a way to know if I am in iTimer VM?

by Eliot Miranda

Hi Mariano, On May 16, 2017, at 6:35 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: Guys, As you know, OSSubprocess does not work correctly in Linux unless you use the iTimer VM. As others have pointed out, you mean that OSSubprocess does not work correctly unless you use the threaded heartbeat VM. That the itinerary heartbeat breaks OSSubprocess. I would like to open a warning (that growl thingy on bottom left of the screen) or something at loading / install time if I can detect I am under Linux AND under traditional linux VM (not itimer). Do you know how can I do that? I made a mistake in that there is no way, other than by using the FFI, to discover if the timer heartbeat is being used. Would it be satisfactory if I provide a flag in vm parameter 48 that, if set, indicates the itimer heartbeat is in use? This could be done in a few minutes and would be ready for the official release of Pharo 6. -- Mariano http://marianopeck.wordpress.com

May 16, 2017

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

by Ben Coman

On Tue, May 2, 2017 at 10:36 PM, Raffaello Giulietti <raffaello.giulietti(a)lifeware.ch> wrote: > 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. > > 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? I just bumped into this which you may find interesting... https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/platforms/unix/v… * The upshot of all this is that Squeak will claim (and hold on to) * ALL of the available virtual memory (or at least 75% of it) when * it starts up. If you can't live with that, use the -memory * option to allocate a fixed size heap. cheers -ben

May 16, 2017

Re: [Pharo-dev] Is there a way to know if I am in iTimer VM?

by Mariano Martinez Peck

On Tue, May 16, 2017 at 11:00 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > On 16 May 2017 15:36, "Mariano Martinez Peck" <marianopeck(a)gmail.com> > wrote: > > Guys, > > As you know, OSSubprocess does not work correctly in Linux unless you use > the iTimer VM. I would like to open a warning (that growl thingy on bottom > left of the screen) or something at loading / install time if I can detect > I am under Linux AND under traditional linux VM (not itimer). > > > I thought it was the other way around, it doesn't work properly in itimer, > only in threaded heartbeat? > > yes, sorry, I said it the wrong way!. > Cheers, > Alistair > > > -- Mariano http://marianopeck.wordpress.com

May 16, 2017

Re: [Pharo-dev] Is there a way to know if I am in iTimer VM?

by Alistair Grant

On 16 May 2017 15:36, "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: Guys, As you know, OSSubprocess does not work correctly in Linux unless you use the iTimer VM. I would like to open a warning (that growl thingy on bottom left of the screen) or something at loading / install time if I can detect I am under Linux AND under traditional linux VM (not itimer). I thought it was the other way around, it doesn't work properly in itimer, only in threaded heartbeat? Cheers, Alistair

May 16, 2017

Re: [Pharo-dev] Is there a way to know if I am in iTimer VM?

by Mariano Martinez Peck

OK... yeah, I don't know if that's accessible to the VM. And related questions... could it be that for 6.0 the "default" linux VM is now threaded heartbeat rather than itimer? That looks like based on [1]. Also, for Pharo 5.0 which is the official place to download the threaded heartbeat Linux 32 bits VM? Please can someone confirm? Thanks in advance, https://bintray.com/opensmalltalk/vm/cog#files On Tue, May 16, 2017 at 10:42 AM, Max Leske <maxleske(a)gmail.com> wrote: > The --version command line option to the VM prints "ITHB" as part of the > version for itimer VM's. Not sure whether that is accessible from within > the image though. > > Cheers, > Max > > On 16 May 2017, at 15:35, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > Guys, > > As you know, OSSubprocess does not work correctly in Linux unless you use > the iTimer VM. I would like to open a warning (that growl thingy on bottom > left of the screen) or something at loading / install time if I can detect > I am under Linux AND under traditional linux VM (not itimer). > > Do you know how can I do that? > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Mariano http://marianopeck.wordpress.com

May 16, 2017