OK, I'll give it a try tomorrow and let the mailing list know about the
outcome.
On 2017-05-02 18:30, Denis Kudriashov wrote:
Could you check how it works with Pharo5 which was based on prespur CogVM?
2017-05-02 16:36 GMT+02:00 Raffaello Giulietti
<raffaello.giulie...@lifeware.ch <mailto:raffaello.giulie...@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.
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
