Open Lestropie opened 5 years ago
I'm not sure if this can still be reproduced (I think someone on the forum reported something somewhat related), but I think this is potentially a consequence of relying on qApp->processEvents()
. From the Qt's documentation:
Use of this function is discouraged. Instead, prefer to move long operations out of the GUI thread into an auxiliary one and to completely avoid nested event loop processing. If event processing is really necessary, consider using QEventLoop instead.
Is this the same issue as discussed on the forum recently? I've looked into it, and I couldn't see a simple fix. That progressbar is a real problem...
In the meantime, the simplest way around it is to add the -quiet
option to your mrview
command, which prevents the progressbar from showing at all...
Have hit this one a few times, but always when madly trying to put figures together, so have never pursued it.
Occurs for both 3D and 4D overlay images. Either case works fine if the overlay is loaded from the GUI rather than the command-line.
My suspicion is that there's a code path whereby something is trying to access the value of some element of the overlay toolbar, but use of command-line options related to toolbars when executing
mrview
does not in fact open those toolbars, and hence that element is uninitialised. Unfortunately the traceback is not overly helpful even with QT debugging symbols installed.Appears to not be the same as #871.
The progress bar for loading the overlay image into memory appears, gets to 100%, and closes, before the segfault occurs.