Re: [basex-talk] GUI doesn't quit on Mac

[Joe Wicentowski]

As a Mac user, I do not generally expect closing a window via the red
window button to quit an app. With only a few exceptions (e.g., single
window only apps like the Calculator), closing any/all of an app's windows
will keep the app open; apps that remain open after their windows are
closed generally take a click on the app's Dock icon as a signal to open a
new window.

But I do expect that selecting Quit via the menu bar will fully quit the
app. Respecting that Quit command is far more important than treating the
red window button as a request to Quit.

A few times I've needed to restart my Mac to install a software update or
finish installing a piece of software. Typically, these processes present
the user with a dialog to trigger the restart, which, when accepted, causes
the OS to quit all open apps. In this scenario, BaseX causes the restart to
fail, because it will not quit when told, and the restart will time out
unless you find out how to quit it. (I use control-C in the Terminal window
where I ran the `basexgui` command.)

I hope this sheds some light on the matter. Thanks!

On Tue, Nov 8, 2022 at 3:11 PM Majewski, Steven Dennis (sdm7g) <
sd...@virginia.edu> wrote:

> It looks like it does exit, after a short delay, when closed by clicking
> the red button on the window, instead of quoting from the menu.
>
> — Steve.
>
>
> On Nov 8, 2022, at 3:04 PM, Christian Grün 
> wrote:
>
> Thanks for the observation. Mac support was improved in general with Java
> 11, but it still requires some OS-specific tweaks in the code. Our current
> solution may not be complete enough to achieve the expected default
> behavior [1].
>
> I’m no Mac user, but does it make a difference if the GUI is quit a) via
> the menu or b) the red icon?
>
> [1]
> https://github.com/BaseXdb/basex/blob/main/basex-core/src/main/java/org/basex/gui/layout/BaseXLayout.java#L584
>
>
>
> Joe Wicentowski  schrieb am Di., 8. Nov. 2022, 20:54:
>
>> I've been experiencing this problem too on macOS (both 12 Monterey and
>> now 13 Ventura), installed via Homebrew, and started via the `basexgui`
>> command line command.
>>
>> On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) <
>> sd...@virginia.edu> wrote:
>>
>>> I’ve been having a problem for a while where after attempting to quit
>>> the Mac GUI, it doesn’t actually exit and has to be force quit. I’m sorry I
>>> wasn’t able to track how this tracks with MacOS / JDK / BaseX updates and
>>> when it actually started happening. Wondering if anyone else has had this
>>> issue, and whether it’s Mac specific or JDK version specific.
>>>
>>>
>>> MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
>>> Openjdk from home-brew install — currently openjdk/19.0.1, but was
>>> happening on earlier versions.
>>> And the current and last several versions of BaseX
>>>
>>> — Steve M.
>>>
>>>
>>>
>

Re: [basex-talk] GUI doesn't quit on Mac

[Majewski, Steven Dennis (sdm7g)]

It looks like it does exit, after a short delay, when closed by clicking the 
red button on the window, instead of quoting from the menu. 

— Steve. 


> On Nov 8, 2022, at 3:04 PM, Christian Grün  wrote:
> 
> Thanks for the observation. Mac support was improved in general with Java 11, 
> but it still requires some OS-specific tweaks in the code. Our current 
> solution may not be complete enough to achieve the expected default behavior 
> [1].
> 
> I’m no Mac user, but does it make a difference if the GUI is quit a) via the 
> menu or b) the red icon?
> 
> [1] 
> https://github.com/BaseXdb/basex/blob/main/basex-core/src/main/java/org/basex/gui/layout/BaseXLayout.java#L584
>  
> 
> 
> 
> 
> Joe Wicentowski mailto:joe...@gmail.com>> schrieb am Di., 
> 8. Nov. 2022, 20:54:
> I've been experiencing this problem too on macOS (both 12 Monterey and now 13 
> Ventura), installed via Homebrew, and started via the `basexgui` command line 
> command.
> 
> On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) 
> mailto:sd...@virginia.edu>> wrote:
> I’ve been having a problem for a while where after attempting to quit the Mac 
> GUI, it doesn’t actually exit and has to be force quit. I’m sorry I wasn’t 
> able to track how this tracks with MacOS / JDK / BaseX updates and when it 
> actually started happening. Wondering if anyone else has had this issue, and 
> whether it’s Mac specific or JDK version specific. 
> 
> 
> MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
> Openjdk from home-brew install — currently openjdk/19.0.1, but was happening 
> on earlier versions. 
> And the current and last several versions of BaseX 
> 
> — Steve M. 
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: [basex-talk] GUI doesn't quit on Mac

[Christian Grün]

Thanks for the observation. Mac support was improved in general with Java
11, but it still requires some OS-specific tweaks in the code. Our current
solution may not be complete enough to achieve the expected default
behavior [1].

I’m no Mac user, but does it make a difference if the GUI is quit a) via
the menu or b) the red icon?

[1]
https://github.com/BaseXdb/basex/blob/main/basex-core/src/main/java/org/basex/gui/layout/BaseXLayout.java#L584



Joe Wicentowski  schrieb am Di., 8. Nov. 2022, 20:54:

> I've been experiencing this problem too on macOS (both 12 Monterey and now
> 13 Ventura), installed via Homebrew, and started via the `basexgui` command
> line command.
>
> On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) <
> sd...@virginia.edu> wrote:
>
>> I’ve been having a problem for a while where after attempting to quit the
>> Mac GUI, it doesn’t actually exit and has to be force quit. I’m sorry I
>> wasn’t able to track how this tracks with MacOS / JDK / BaseX updates and
>> when it actually started happening. Wondering if anyone else has had this
>> issue, and whether it’s Mac specific or JDK version specific.
>>
>>
>> MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
>> Openjdk from home-brew install — currently openjdk/19.0.1, but was
>> happening on earlier versions.
>> And the current and last several versions of BaseX
>>
>> — Steve M.
>>
>>
>>

Re: [basex-talk] GUI doesn't quit on Mac

[Joe Wicentowski]

I've been experiencing this problem too on macOS (both 12 Monterey and now
13 Ventura), installed via Homebrew, and started via the `basexgui` command
line command.

On Tue, Nov 8, 2022 at 1:02 PM Majewski, Steven Dennis (sdm7g) <
sd...@virginia.edu> wrote:

> I’ve been having a problem for a while where after attempting to quit the
> Mac GUI, it doesn’t actually exit and has to be force quit. I’m sorry I
> wasn’t able to track how this tracks with MacOS / JDK / BaseX updates and
> when it actually started happening. Wondering if anyone else has had this
> issue, and whether it’s Mac specific or JDK version specific.
>
>
> MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
> Openjdk from home-brew install — currently openjdk/19.0.1, but was
> happening on earlier versions.
> And the current and last several versions of BaseX
>
> — Steve M.
>
>
>

[basex-talk] GUI doesn't quit on Mac

[Majewski, Steven Dennis (sdm7g)]

I’ve been having a problem for a while where after attempting to quit the Mac 
GUI, it doesn’t actually exit and has to be force quit. I’m sorry I wasn’t able 
to track how this tracks with MacOS / JDK / BaseX updates and when it actually 
started happening. Wondering if anyone else has had this issue, and whether 
it’s Mac specific or JDK version specific. 


MacOS 12.6.1 but problem goes back at least to earlier 12.6 versions
Openjdk from home-brew install — currently openjdk/19.0.1, but was happening on 
earlier versions. 
And the current and last several versions of BaseX 

— Steve M. 




smime.p7s
Description: S/MIME cryptographic signature

Re: [basex-talk] Reported memory usage in GUI with Store Module

[Christian Grün]

Hi Tim,

Thanks for testing the new Store Module.

The fluctuations in memory consumption and the long lags mainly
indicate that the garbage collector is pretty busy. Some data
structures will be much smaller if serialized to disk, so I assume
your amount of data is simply too large to be efficiently organized in
main memory. If you need all data in practce, you could think about
only preserving meta data and index structures in memory.

Feel free to provide us with test cases if you feel that the behavior
is suspicious enough.

Cheers,
Christian


On Tue, Nov 8, 2022 at 5:53 AM Tim Thompson  wrote:
>
> Hello,
>
> I've been experimenting with the new Store module, which seems very handy. I 
> have a custom store that is about 2GB in size. In the GUI (BaseX 10.3 beta), 
> when I try to load it into memory with store:read(), the reported memory 
> usage appears to max out (with 32GB of available memory):
>
> Total Memory: 32 GB
> Reserved Memory: 32 GB
> Used Memory: 32 GB
>
> However, monitoring memory usage with htop shows a smaller increase in memory 
> usage: from 5GB at baseline, it peaks around 15GB, then goes down to 9GB, all 
> while the BaseX GUI appears to be frozen.
>
> After a couple of minutes, the store does load, but GUI performance seems to 
> be degraded, and it continues to report max memory usage.
>
> Any thoughts?
>
> Tim
>
>
> --
> Tim A. Thompson (he, him)
> Librarian for Applied Metadata Research
> Yale University Library
> www.linkedin.com/in/timathompson
>