[Octave-bug-tracker] [bug #53867] Octave startup is extremely slow

[anonymous]

Follow-up Comment #8, bug #53867 (project octave):

OK, it seems that the issue is not related to Octave itself because the delay
occurs before Octave's main function is executed.


Octave-4.2.2
$ date '+%s';  printf "break main\nrun -f -W --eval \"x=pi\"\nprint
time(0)\ncont\nquit\n" | gdb /bin/octave-cli.exe; date '+%s'
1526378996
GNU gdb (GDB) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from C:/Octave/OCTAVE~1.2/bin/octave-cli.exe...(no debugging
symbols found)...done.
(gdb) Breakpoint 1 at 0x402df1
(gdb) Starting program: C:\Octave\OCTAVE~1.2\bin\octave-cli.exe -f -W --eval
"x=pi"
[New Thread 11000.0x2548]

Breakpoint 1, 0x0000000000402df1 in octave-cli!main ()
(gdb) $1 = 1526378998
(gdb) Continuing.
x =  3.1416
[Inferior 1 (process 11000) exited normally]
(gdb) 1526378999



Octave-4.4.0
$ date '+%s';  printf "break main\nrun -f -W --eval \"x=pi\"\nprint
time(0)\ncont\nquit\n" | C:/Octave/Octave-4.2.2/bin/gdb.exe
/bin/octave-cli.exe; date '+%s'
1526378846
GNU gdb (GDB) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from C:/Octave/OCTAVE~1.0/bin/octave-cli.exe...(no debugging
symbols found)...done.
(gdb) Breakpoint 1 at 0x402e01
(gdb) Starting program: C:\Octave\OCTAVE~1.0\bin\octave-cli.exe -f -W --eval
"x=pi"
[New Thread 6660.0x2628]
[New Thread 6660.0x287c]
[New Thread 6660.0x2668]
[New Thread 6660.0x2978]
[New Thread 6660.0x22f8]
[New Thread 6660.0x16d4]
[New Thread 6660.0x26a8]
[New Thread 6660.0xc60]
warning: ERROR !!! HeapSetInformation failed to set g_Heap to LFH
warning: ERROR !!! HeapSetInformation failed to set g_SpyHeap to LFH
[New Thread 6660.0x2b08]
[New Thread 6660.0x1d44]

Thread 1 hit Breakpoint 1, 0x0000000000402e01 in octave-cli!main ()
(gdb) $1 = 1526378870
(gdb) Continuing.
[New Thread 6660.0x2468]
x =  3.1416
[Thread 6660.0x287c exited with code 0]
[Thread 6660.0x26a8 exited with code 0]
[Thread 6660.0x2468 exited with code 0]
[Thread 6660.0x1d44 exited with code 0]
[Thread 6660.0x2978 exited with code 0]
[Thread 6660.0x16d4 exited with code 0]
[Thread 6660.0xc60 exited with code 0]
[Thread 6660.0x22f8 exited with code 0]
[Thread 6660.0x2b08 exited with code 0]
[Thread 6660.0x2668 exited with code 0]
[Inferior 1 (process 6660) exited normally]
(gdb) 1526378871


                                        4.2.2           4.4
time before gdb starts:  t0             1526378996      1526378846
time before main starts: t1             1526378998      1526378870
time after gdb exits:    t2             1526378999      1526378871
time delay before main:  t1 - t0                 2              24
time delay within main:  t2 - t1                 1               1


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53867>

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