Thanks for the answer. It happens after hours of execution with more
logging than normal: Debugging code added which ,ight have triggered a
race condition (Or maybe another problem).
Btw, had a quick check with valgrind which reported a couple of of read
accesses to unitialised memory.
Thanks
R
Le 06.11.2011 11:54, Josh Rovero a écrit :
On Sun, Nov 6, 2011 at 8:45 AM, [email protected]
<[email protected]> wrote:
Hi,
At the moment, I am testing some changes on fldigi and noticed that it stays
stuck with 200% CPU (I have atwo-cores processors). Here is where the
threads are stuck:
Remi,
On 3.22.0AX, fedora core 15/14, x86_64, built with --enable-debug....
FC15, AMD Athlon 64x2 4200+ -- two instances of fldigi, each with
about 45% of CPU and 2.5% of memory.
FC14, AMD Opteron 1218 dual core -- one instance of fldigi, 15% of cpu
I'm not seeing the issue you report in this version, but
do not know what other changes you may have made...
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
