[Octave-bug-tracker] [bug #59331] Processor load stays up after `__run_test_suite__`

[Markus Mützel]

Follow-up Comment #9, bug #59331 (project octave):

I'm also not familiar with the GUI code. So I don't know if I'm of much help
here.

I ran the test suite again. That triggered the familiar state with the laggy
GUI.
I attached gdb to the octave process, set at breakpoint in
`octave::main_window::notice_settings` and continued execution.
Once the breakpoint was hit, I continued execution step by step until gdb
became irresponsive. Execution didn't return from the gdb session to the
Octave process I guess. At least, I couldn't interact with the GUI.
At that point, CPU load was high again and it was back to perpetually writing
to octave-gui.ini.ABCDEF files.

Attaching a copy of the gdb session.

(file #50114)
    _______________________________________________________

Additional Item Attachment:

File name: debug_after_BISTs.txt          Size:5 KB
    <https://file.savannah.gnu.org/file/debug_after_BISTs.txt?file_id=50114>



    _______________________________________________________

Reply to this item at:

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

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