[hpsdr] Observations on the new HPSDR firmware/PowerSDR

[Dan Quigley]

Thanks Bill, I have the symbol files now. 

I've had the rx part of the system running all day today and have not had to
restart PowerSDR. I now think we are dealing with two different problems.
Interesting that no transmit avoids the degradation issue I reported.

I'll start another cold start test tomorrow and see how things go.  

Best,
Dan

-----Original Message-----
From: Bill Tracey [mailto:bill at ewjt.com] 
Sent: Monday, June 01, 2009 9:45 PM
To: Dan Quigley; hpsdr at openhpsdr.org
Subject: RE: [hpsdr] Observations on the new HPSDR firmware/PowerSDR

Hi Dan,

I agree with you this is likely a PowerSDR glitch - not entirely sure 
how it relates to some of the other oddness folks are seeing.

I've posted a new build tonight which has symbols for DttSP.dll, 
JanusAudio.dll and PowerSDR.exe .   The code is 
here: 
svn://206.216.146.154/svn/repos_sdr_windows/PowerSDR/branches/kd5tfd/PennyMe
rge/bin 
- the .pdb files in Release-Syms need to be moved to Release for 
tools to find them.

Regards,

Bill



At 12:22 AM 6/1/2009, Dan Quigley wrote:
>Hi Bill,
>
>Yes I am using Process Explorer.  This is an odd one, but I believe it is
>germane to problems others have reported.  The length of time appears to be
>random from my experience. (after today from 0 to a couple of hours)  I am
>90% convinced it is a PowerSDR issue and related to (or exacerbated by)
>sample rate but I have not found a reproducible trigger.  There may be a
>correlation to the GC - I watched the .NET runtime and its memory heap was
>definitely fluid during PowerSDR abnormal operations but that may be a
>reaction to something else.  This does smell a bit like a race condition
>issue but it is too early to be sure.
><....>
>If you can send or point me to PowerSDR release symbol files, my stack
>traces may be more helpful...
>
>Best,
>Dan




 1243920522.0