|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #59331] Processor load stays up after `__run_test_suite__` |
Date: | Mon, 26 Oct 2020 13:16:52 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 |
Follow-up Comment #8, bug #59331 (project octave): In the resource_manager constructor, there is some attempt to copy existing resource files for the new system-dependent file name/location. It looks like we are leaving that decision to Qt with QSettings::IniFormat. I don't know exactly how that process is supposed to work. Maybe some kind of signal/slot loop is happening? Or are there specific tests that would access the GUI config file and cause Octave to try to rewrite it (as it appears is happening)? I don't know enough about how this is supposed to work. Can you use the debugger and step to see what actions are happening while it is in this state? Is it possible to identify what is causing the apparent infinite loop? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59331> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |