On Jun 30, 2013 8:44 AM, "Howie Hoyt" <howie...@gmail.com> wrote:
>
> Switched over to a box running win/xp.
> This is a single processor @ 3ghz with chrome in background.
>
> CPU saturates on "querying installed hamlib backends"
>
> I show 6421 handles, 392 Threads.
> Memory usage not a problem (1.6gb free).
>
> Finally killed it as the processor stayed at 100% and 60% completion 'querying hamlib backends' after many minutes and started to worry about cpu overheating.
>
> Thinking it was that i had not rebooted, tried that. Same situation. Decided to wait it out, relying on cpu fan to keep it cool.
>
> After maybe 5min it did complete. I do not have rigs hooked up, but all seems ok once you get past the query of hamlib backends.
>
> After the check did complete, subsequent startups to so2sdr do bring it up very quickly.
Yes, this is a problem I am aware of. For some reason the same code on Linux finishes in milliseconds but takes several minutes on Windows. It is querying hamlib to see what backends are installed, it only needs to do this the first time it runs or if the hamlib version changes. Afterwards it saves the list to disk.
>
> Tor can you reproduce program exception 5 when taking down SO2SDR w/o rigs attached ? (WinXP) ?
> offset in so2sdr.exe = 00058182
>
I will check.
Tor
> 73, Howie N4AF
>
> --
> You received this message because you are subscribed to the Google Groups "so2sdr" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to so2sdr+un...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--