[Octave-bug-tracker] [bug #60620] octave-cli crashes when interacting with Java libraries

[Markus Mützel]

Follow-up Comment #36, bug #60620 (project octave):

As some points of reference:
https://lists.gnu.org/archive/html/bug-coreutils/2009-10/msg00262.html
> The default thread stack size is:
>  - glibc i386, x86_64    7.4 MB
>  - Tru64 5.1             5.2 MB
>  - Cygwin                1.8 MB
>  - Solaris 7..10           1 MB
>  - MacOS X 10.5          460 KB
>  - AIX 5                  98 KB
>  - OpenBSD 4.0            64 KB
>  - HP-UX 11               16 KB

https://docs.microsoft.com/en-us/cpp/build/reference/stack-stack-allocations?view=msvc-160
> For ARM, x86 and x64 machines, the default stack size is 1 MB.
(That is for MSVC. I'm not sure if it is the same for mingw.)


https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html
> Xsssize
> Sets the thread stack size (in bytes). Append the letter k or K to indicate
KB, m or M to indicate MB, g or G to indicate GB. The default value depends on
the platform:
>
> Linux/ARM (32-bit): 320 KB
>
> Linux/i386 (32-bit): 320 KB
>
> Linux/x64 (64-bit): 1024 KB
>
> OS X (64-bit): 1024 KB
>
> Oracle Solaris/i386 (32-bit): 320 KB
>
> Oracle Solaris/x64 (64-bit): 1024 KB
https://docs.oracle.com/javase/8/docs/technotes/tools/windows/java.html
> The default value depends on virtual memory.

So IIUC, on glibc x86_64, loading the JVM reduces the default stack size from
7.4 MiB to 1 MiB, or from 7.4 MiB to 320 kiB on glibc i386.
That seems to affect all (new?) threads, not only those of the JVM.

In bug #58641, we added a test and set default values for a different JVM
switch for a similar issue. Should we do something like this here, too?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60620>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/