Hi
I have the same situation.
Running Linux Mint 20.3 and wsjtx2.7.0-rc1 built from source.
The Optimising Decoder FFT dialog only pops up (intentionally) if the
fail to mem_qmap dialog is on the screen for some time although it's
less than the 15 seconds stated in the code comments, more like 1.5. So
not related to the issue.
Dismissing both dialogs allows wsjtx to run normally (as far as I can
see) on linux.
I did a bit of diagnostics. The code is at widgets | mainwindow.cpp
lines 472 -47 9. I used the default config and a clone of the default
config both unchanged.
//AttachorcreateamemorysegmenttobesharedwithQMAP.
intmemSize=4096;
if(!mem_qmap.attach()){
if(!mem_qmap.create(memSize)){
MessageBox::information_message(this,
"Unabletocreatesharedmemorysegmentmem_qmap.");
}
}
This code runs when wsjtx is first instantiated, before any app windows
appear. It creates the shared memory segment and links the app to it OK.
Normal operation proceeds. When the Op changes to another configuration
the code is run again and _wsjtx is still attached_.
(mem_qmap.isAttached returns true). Consequently mem_qmap.attach fails
and the code tries to create the shared memory segment again which also
fails because the previous shared memory segment and key still exist.
Hence the dialog
Should mem_qmap and it's key have been disposed of when wsjtx terminated
as the configuration was changed? Perhaps it would be better to test
whether the shared memory segment exists and is attached or not rather
than just attempting to attach it.
My reading of the situation is that both dialogs can safely be dismissed
and wsjtx will run OK since the shared memory segment is attached.
73s
Rick (GM4JIB)
On 01/06/2023 17:14, Erik Icket via wsjt-devel wrote:
Dear developers,
When switching to a predefined configuration, an information dialog pops up
with the message 'Unable to create shared memory segment mem-qmap',
followed by another modal message a few secs later 'Optimizing FFTs for your
CPU. Please be patient ...'
After that, the program does not respond anymore. Aborting the program and
restarting brings back the original config.
73's Erik
ON4PB
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
