Yes, I mean the value displayed in that dialog box. On my machine (Mac OS X 10.9.5), the CPU used by BaseX 8.1 turns out to be 218%, even when I am not querying anything (so I guess the memory problem causes this). If I use BaseX 7.9, everything is fine. So now I am using an older version of BaseX.

I can also say that the same problem happens on another mac (OS X Yosemite 10.10.2). Thanks

2015-03-28 14:07 GMT+01:00 Christian GrĂ¼n <christian.gruen@gmail.com>:
Hi Joseph,

> When I open Basex 8.3 GUI, the value of the used memory keeps growing
> up/changing fast, even though I do not do anything. Since this does not
> happen with Basex 7.9, is this due to Java? (I run Java 1.8.X)

I noticed that the memory dialog window (which is shown if you click
on the memory display in the lower right corner of the GUI) is updated
nonstop. Maybe you are you refering to this (unexpected) behavior? I
have just added a GitHub for this [1].

If you refer to memory usage in generally, all I can say is that the
memory consumption, which is indicated by a java instance, is not
necessarily the amount of memory that's currently used by the JVM. I
have also observed that the behavior differs with each Java version.

I didn't notice any unexpected behavior by myself, but feel free to
give me an update if you should encounter things like out of memory.
You could e.g. limit available memory in the basexgui script to e.g.
64m, using the -Xmx64m flag, and observe if the GUI can cope with
that.

Best,
Christian

[1] https://github.com/BaseXdb/basex/issues/1118


>
> Thanks,
> Joseph