[linrad] xlinrad 02.05

[comcast.net; w3sz@xxxxxxxxxxxxxxxx>]

Hello, All,

I have been playing with xlinrad-02.05 some more.

Moving the mouse is still the culprit that causes crashes better than anything else I do.

I do not see a spike on the System Monitor CPU usage [or on the Linrad CPU usage indicator], but perhaps the spike is too brief.  

My system runs about 15% or less CPU usage with 96000 Hz sampling, 4 channel input.

When I run  'valgrind xlinrad', then CPU usage is 98%PLUS and it is not possible to make xlinrad crash with anything I have done.  xlinrad runs very slowly, and there is a speed error with the sampling rate only 35000-48000 instead of 96000.  And I can move the windows, even the Smeter window which I can't move normally, with no errors.  So it seems like overloading the CPU so that Linrad runs at a crawl stops the X windows errors.  Too bad Linrad can't make decent audio when running thru valgrind ;)

I would think that if the crashing problems with mouse movement etc were a CPU overload problem, xlinrad would crash more rather than less with this high% CPU usage and obvious overload when running valgrind xlinrad.

Valgrind complains about more than 100,000 errors in a very short time.  Nearly all of the errors complain about uninitialized values.  Here are the last few lines of the error output:

==22181== Use of uninitialised value of size 4
==22181==    at 0x80BDE57: lir_setpixel (xsys.c:230)
==22181==    by 0x80D3919: update_wg (in /home/linrad/linrad-new/linrad-02-X11.05/xlinrad)
==22181==
==22181== Conditional jump or move depends on uninitialised value(s)
==22181==    at 0x80BDE6F: lir_setpixel (xsys.c:232)
==22181==    by 0x80D3919: update_wg (in /home/linrad/linrad-new/linrad-02-X11.05/xlinrad)
==22181==
==22181== More than 100000 total errors detected.  I'm not reporting any more.
==22181== Final error counts will be inaccurate.  Go fix your program!
==22181== Rerun with --error-limit=no to disable this cutoff.  Note
==22181== that errors may occur in your program without prior warning from
==22181== Valgrind, because errors are no longer being displayed.
==22181==
==22181==
==22181== ERROR SUMMARY: 100000 errors from 103 contexts (suppressed: 35 from 2)==22181== malloc/free: in use at exit: 4,547,028 bytes in 18 blocks.
==22181== malloc/free: 203 allocs, 185 frees, 48,727,298 bytes allocated.
==22181== For counts of detected errors, rerun with: -v
==22181== searching for pointers to 18 not-freed blocks.
==22181== checked 63,354,004 bytes.
==22181==
==22181== LEAK SUMMARY:
==22181==    definitely lost: 136 bytes in 2 blocks.
==22181==      possibly lost: 476 bytes in 7 blocks.
==22181==    still reachable: 4,546,416 bytes in 9 blocks.
==22181==         suppressed: 0 bytes in 0 blocks.
==22181== Use --leak-check=full to see details of leaked memory.
--------------------------------------------------------------------

I will put the whole error file at 
http://www.nitehawk.com/w3sz/xlinrad.log

It will take me a few minutes to put it there.

I hope some of the above helps. 

73,

Roger
W3SZ

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@xxxxxxxxxxxxxxxxxxxxx>.
To unsubscribe, E-mail to: <linrad-off@xxxxxxxxxxxxxxxxxxxxx>
To switch to the DIGEST mode, E-mail to <linrad-digest@xxxxxxxxxxxxxxxxxxxxx>
To switch to the INDEX mode, E-mail to <linrad-index@xxxxxxxxxxxxxxxxxxxxx>
Send administrative queries to  <linrad-request@xxxxxxxxxxxxxxxxxxxxx>


LINRADDARNIL