|
Mark / Ohio
|
 |
« Reply #25 on: November 02, 2009, 12:41:45 AM » |
|
I wonder if the lockup point is related to the amount RAM installed versus RAM in use in the computer?
IIRC mine would lock around 150-200Mb when I had the problem. It would take about a day for it to reach that point. Right now I'm not seeing it on either of my computers. (Knocking on wood and fingers crossed while typing.)
|
|
|
|
|
Logged
|
Mark 2002 Davis VP I Wireless, WeatherLink (Serial), VWS, ImageSalsa, GRLevel3, VirtualVP, VPLive, StartWatch, Windows XP (SP3)
|
|
|
|
mackbig
|
|
« Reply #26 on: November 02, 2009, 06:43:28 AM » |
|
I may have jynxed myself. my pc "recovered from a serious error" between 12:45 and 3:15 am last night(depending which time stamped I believe last GR3 update was 12:45am, all my uploads failed from 2am to 3:20am, and after that only WD and GR3 were the only failes). WD is still in trial so autostart doesnt work, and Gr3 does not have autostart capabilities.
Fluke? or vws finally crashed the system. we'll see next time.
Andrew
|
|
|
|
|
Logged
|
 Andrew - Davis VP2+ 6163, serial weatherlink, wireless anemometer, running Weather Display. Boltek PCI Stormtracker, Astrogenic Nexstorm, Strikestar - UNI, CWOP CW8618, GrLevel3, (Station 2 OS WMR968, VWS 13.01p09), Windows 7-64 |
|
|
|
DaculaWeather
|
|
« Reply #27 on: November 02, 2009, 12:38:54 PM » |
|
I don't know if p100 solved my issues or not but so far after about two weeks, rock solid. No restarts, memory at 82mb or so.
|
|
|
|
|
Logged
|
Steve Davis Vue, VWS, WDisplay, VVP, StartWatch CWOP   |
|
|
|
W3DRM
|
|
« Reply #28 on: November 02, 2009, 07:56:36 PM » |
|
I wonder if the lockup point is related to the amount RAM installed versus RAM in use in the computer?
IIRC mine would lock around 150-200Mb when I had the problem. It would take about a day for it to reach that point. Right now I'm not seeing it on either of my computers. (Knocking on wood and fingers crossed while typing.) My old Dell Dimension 8250 had only 512MB of memory in it so this summer I add a 1GB chip to it and now have 1.5GB. I saw no change at all in my VWS memory leak problem and the resultant restarts by StartWatch. |
|
|
|
|
Logged
|
Don - W3DRM - Minden, Nevada --- Davis Wireless VP2, VWS 14.00 p101, StartWatch, VirtualVP, VPLive, WL 5.9.3, Win7 Ultimate-SP1 --- Logitech QuickCam Fusion webcam  |
|
|
|
peterc46
|
|
« Reply #29 on: November 23, 2009, 01:51:53 PM » |
|
I used to have vws reboot my machine every night at 1am because I had read about this problem. About a month ago I stopped the rebooting and just let it run 24/7. I have found that it will hover around 30Mb for quite a while, then slowly creep up - after a week it got to 88Mb. But then I noticed something interesting - try this:
On the PC with vws, open the Task Manager and go to the Processes tab. Highlight the vws entry and note the memory usage. If vws is minimized, open it up, then minimize it again. I found that when I do this the mem value doesn't change when I open the vws display up, but when I minimize the display the mem usage drops right down to 7-8Mb or even less, then the creep starts from there. Using this, there's no need to close and restart vws or the pc when the value gets too big for comfort, just open up the window then minimize it again.
|
|
|
|
|
Logged
|
|
|
|
|
Weather Display
|
|
« Reply #30 on: November 23, 2009, 04:18:16 PM » |
|
yes, thats a quirk of windows, where minimising a program frees up GUI resources
|
|
|
|
|
Logged
|
|
|
|
|
Mark / Ohio
|
|
« Reply #31 on: November 23, 2009, 09:23:46 PM » |
|
.. I found that when I do this the mem value doesn't change when I open the vws display up, but when I minimize the display the mem usage drops right down to 7-8Mb or even less, then the creep starts from there. Using this, there's no need to close and restart vws or the pc when the value gets too big for comfort, just open up the window then minimize it again.
Interesting! When you have VWS minimized, do you have it minimized to just an icon in the lower right taskbar or do you have it minimized to the taskbar still showing temperature and wind readings? |
|
|
|
|
Logged
|
Mark 2002 Davis VP I Wireless, WeatherLink (Serial), VWS, ImageSalsa, GRLevel3, VirtualVP, VPLive, StartWatch, Windows XP (SP3)
|
|
|
|
peterc46
|
|
« Reply #32 on: November 23, 2009, 09:39:46 PM » |
|
Interesting! When you have VWS minimized, do you have it minimized to just an icon in the lower right taskbar or do you have it minimized to the taskbar still showing temperature and wind readings?
That doesn't seem to make any difference. If you start vws 'hidden', it simply puts an icon in the Systray. If you click that icon to view the display, then minimize it, the effect I described still happens but the program does not just go back to the Systray, you end up with an icon in the task bar at the bottom of the screen as well. |
|
|
|
|
Logged
|
|
|
|
|
Mark / Ohio
|
|
« Reply #33 on: November 23, 2009, 10:30:08 PM » |
|
You can also double click the icon and hide it again too. Did not know if you had found that feature yet.  I was wondering if keeping it hidden would solve the leak for you. |
|
|
|
|
Logged
|
Mark 2002 Davis VP I Wireless, WeatherLink (Serial), VWS, ImageSalsa, GRLevel3, VirtualVP, VPLive, StartWatch, Windows XP (SP3)
|
|
|
|
mackbig
|
|
« Reply #34 on: November 23, 2009, 10:58:07 PM » |
|
Interesting. Mine stays hidden in sys tray all the time. I just checked, and it was up to 175MB after 5 days.
I maximized, then minimized, went to 125MB.
I maximized again, and left it maximinzed for a few minutes, then all of a sudden it was only showing 5MB. hmmm??? 20 minutes later its already at 10meg... Maybe the trick is playing with it.... perhaps vws gets lonely if left minimized to do its work.
Andrew
|
|
|
|
|
Logged
|
Andrew - Davis VP2+ 6163, serial weatherlink, wireless anemometer, running Weather Display. Boltek PCI Stormtracker, Astrogenic Nexstorm, Strikestar - UNI, CWOP CW8618, GrLevel3, (Station 2 OS WMR968, VWS 13.01p09), Windows 7-64 |
|
|
|
W3DRM
|
|
« Reply #35 on: November 24, 2009, 01:09:36 AM » |
|
I upgraded to v14.00 p101 several days ago...
VWS is still restarted 3 to 5 times a day with the new version. Currently VWS is running at about 215MB and will most likely restart again tonight when it reaches the 225MB limit I have set with Startwatch. I have plenty of memory. VWS memory leaks have always been problematic for me since I installed it 4 years ago. Guess I'm just going to have to live with it. Startwatch does it magic and keeps things running nicely so I'm satisfied - for the time being... I did try letting it run but it seems to hang up around 250 to 300MB of MemUsage.
One thing I did find out this morning though was that my daily reports were all blank. After installing p101, it seems as though VWS reset all of the fields to be loaded in the File Settings section of setup (and I missed that little detail). Does anyone know if the daily archive reports (in data\archive\daily\yyyymmdd.txt) can be rebuilt either manually or with VWS? The monthly and annual files have repopulated themselves but the daily stuff is nothing but blank lines showing a timestamp only. Perhaps I should have posted this as a separate post...
|
|
|
|
|
Logged
|
Don - W3DRM - Minden, Nevada --- Davis Wireless VP2, VWS 14.00 p101, StartWatch, VirtualVP, VPLive, WL 5.9.3, Win7 Ultimate-SP1 --- Logitech QuickCam Fusion webcam |
|
|
|
mackbig
|
|
« Reply #36 on: November 24, 2009, 06:51:26 AM » |
|
Update. a few minutes after minimizing to tray, popped back up to 120meg, then maximize, went back to 10 meg. odd. I guess the only way to truly restart the memory clock is the close restart. anyway, I get a week plus, before I have to close. Not bad, better than my GR3 performance lately, and at least vws restarts itself fully unattended. Andrew Interesting. Mine stays hidden in sys tray all the time. I just checked, and it was up to 175MB after 5 days.
I maximized, then minimized, went to 125MB.
I maximized again, and left it maximinzed for a few minutes, then all of a sudden it was only showing 5MB. hmmm??? 20 minutes later its already at 10meg... Maybe the trick is playing with it.... perhaps vws gets lonely if left minimized to do its work.
Andrew
|
|
|
|
|
Logged
|
Andrew - Davis VP2+ 6163, serial weatherlink, wireless anemometer, running Weather Display. Boltek PCI Stormtracker, Astrogenic Nexstorm, Strikestar - UNI, CWOP CW8618, GrLevel3, (Station 2 OS WMR968, VWS 13.01p09), Windows 7-64 |
|
|
|
port1
|
|
« Reply #37 on: November 24, 2009, 07:11:03 AM » |
|
Interesting...way interesting. Thanks for that tip. One thing I did notice while monitoring my system is the vast amount of memory used by my Firefox application. Brutal amount!   Henry I used to have vws reboot my machine every night at 1am because I had read about this problem. About a month ago I stopped the rebooting and just let it run 24/7. I have found that it will hover around 30Mb for quite a while, then slowly creep up - after a week it got to 88Mb. But then I noticed something interesting - try this:
On the PC with vws, open the Task Manager and go to the Processes tab. Highlight the vws entry and note the memory usage. If vws is minimized, open it up, then minimize it again. I found that when I do this the mem value doesn't change when I open the vws display up, but when I minimize the display the mem usage drops right down to 7-8Mb or even less, then the creep starts from there. Using this, there's no need to close and restart vws or the pc when the value gets too big for comfort, just open up the window then minimize it again.
|
|
|
|
|
Logged
|
KNYFLORA5 WMR968 VWS v14.00 p73 CoCoRaHS NY-NS-7 CWOP DW1891 SKYWARN 09-148  |
|
|
|
sam2004gp
|
|
« Reply #38 on: November 24, 2009, 12:53:42 PM » |
|
Yes I have noticed even with the latest version how much memory firefox will steal from the system. Of course the more extensions and such, the more the usage.
|
|
|
|
|
Logged
|
|
|
|
|
port1
|
|
« Reply #39 on: November 24, 2009, 06:52:47 PM » |
|
 I have plenty of extensions and add-ons, Sam, and hence the huge memory hog. Yet, I wouldn't live without FireFox, even on a remote, desert island, stranded thousands of miles from home!!!   Henry
|
|
|
|
|
Logged
|
KNYFLORA5 WMR968 VWS v14.00 p73 CoCoRaHS NY-NS-7 CWOP DW1891 SKYWARN 09-148 |
|
|
|
sam2004gp
|
 |
« Reply #40 on: November 24, 2009, 07:31:32 PM » |
|
True, same thing here.
|
|
|
|
|
Logged
|
|
|
|
|
W3DRM
|
|
« Reply #41 on: November 25, 2009, 12:35:08 AM » |
|
I upgraded to v14.00 p101 several days ago...
VWS is still restarted 3 to 5 times a day with the new version. Currently VWS is running at about 215MB and will most likely restart again tonight when it reaches the 225MB limit I have set with Startwatch. I have plenty of memory. VWS memory leaks have always been problematic for me since I installed it 4 years ago. Guess I'm just going to have to live with it. Startwatch does it magic and keeps things running nicely so I'm satisfied - for the time being... I did try letting it run but it seems to hang up around 250 to 300MB of MemUsage.
One thing I did find out this morning though was that my daily reports were all blank. After installing p101, it seems as though VWS reset all of the fields to be loaded in the File Settings section of setup (and I missed that little detail). Does anyone know if the daily archive reports (in data\archive\daily\yyyymmdd.txt) can be rebuilt either manually or with VWS? The monthly and annual files have repopulated themselves but the daily stuff is nothing but blank lines showing a timestamp only. Perhaps I should have posted this as a separate post... Well guess what? - VWS was not restarted by Startwatch last night as I expected. In fact, it has been running fine all day today and is currently sitting at 85MB of MemUsage with an occassional jump to around 120MB and then back to around 85MB. This is the first time I have ever seen this happen on my system. Will have to watch it and see what happens. Maybe, just maybe p101 did change the way VWS is going to run on my system but, I'm not holding my breath. I see no difference whether it is minimized or an active window. |
|
|
|
« Last Edit: November 25, 2009, 12:37:21 AM by W3DRM »
|
Logged
|
Don - W3DRM - Minden, Nevada --- Davis Wireless VP2, VWS 14.00 p101, StartWatch, VirtualVP, VPLive, WL 5.9.3, Win7 Ultimate-SP1 --- Logitech QuickCam Fusion webcam |
|
|
|
sam2004gp
|
|
« Reply #42 on: November 26, 2009, 10:03:48 AM » |
|
My VWS 13.01 is at 19MB - Maximized, reduced to tray went to 8Mb, re-Maximized it want up to 11MB.  |
|
|
|
« Last Edit: November 26, 2009, 10:07:50 AM by sam2004gp »
|
Logged
|
|
|
|
|
