|Subject:||Re: VLF: Tonite... - SpecLab freeze?|
|From:||Markus Vester <[email protected]>|
|Date:||Tue, 7 Mar 2017 14:43:35 -0500|
|Dkim-signature:||v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1488915821; bh=ejDAo5mQOYRcQlay/Y++EpA0Trp028a2exQy4BGFln8=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=A9ypNU9oNeJ3ZFYrzwB23KnRT28le9mx3JQOWYBUk9F8onpySnzBkj14jOP+5DsyX xiQ8h75cdvstc/iUYmKDvp0hl4jeqyxX9kszXf67BsvLeIha7218sCapD+Za+g6pVU NX10FjuJX2zzucaDp0Ng0Bw5Eew1R61617dfmDoI=|
Hi Eddie,On 05/03/2017 15:48, DK7FC wrote:
no problems with freezes from that SpecLab version here so far.
But I do find that Windows10 is not quite kosher regarding continuous operation. I'm running the slow VLF stuff on a convertible laptop under Win10 Home. Within a week or so after a restart, memory usage gradually creeps up from ~ 45 % to 85+%. At that stage, the PC becomes practically inoperable and needs to be rebooted. If I can still manage to shut down SpecLab instances cleanly, saving configuration data can take many minutes instead of a couple of seconds. Such things never occured on the faithful XP machine which is still hosting the LF and Loran grabbers.
To prevent a loss of weeks and months of slowly aquired spectrograms, you could enable SpecLab's file-buffer, which should preserve screen content through a restart (see attached).
Von: g3zjo <[email protected]>
An: rsgb_lf_group <[email protected]>
Verschickt: So, 5. Mrz 2017 22:50
Betreff: Re: VLF: Tonite...
> Then, during the week, i would like to try to send my full callsign to
> Eddie in DFCW-6000. It could work, he can see me day and night it
> seems :-)
Yes that will be worth a try, I should have a stable set up ready, I
have had a display freeze on my EbNaut instance so I shall miss the
Sunday night transmission.
I think Speclab v2.92 b02 suffers from display freeze, I used to run 8
to 10 instances without problems now the 4th instance seems to produce
problems and one of the instances will or may freeze, not necessarily
the last instance or an intensive (20uHz or 5uHz) one either. I wonder
if anyone else is experiencing this.
I have seen frozen displays still exporting updated screen captures too,
a case of WYSINWYG (what you see is not what you get).
It is a very difficult thing to test because of course I don't want to
induce it, the processor load is only 15% with 4 instances running.
73 Eddie G3ZJO
|<Prev in Thread]||Current Thread||[Next in Thread>|