Closing gauges display causes C2 to crash

RayProudfoot · **Posted:** Sun Oct 04, 2009 9:24 am

Steve,

Over the last week I've been running C2 more or less all the time. For info I'm also running C1 and WeatherLink via VPP.

On two occasions when I've had the gauges window open for several hours when I close it it's caused C2 to crash. (View-Gauges). The option to send the report to Microsoft is useless of course but I can't redirect it to you.

When it next happens is there any information you would like? Are you able to replicate this yourself?

steve · **Posted:** Sun Oct 04, 2009 10:01 am

RayProudfoot wrote:

The option to send the report to Microsoft is useless of course

Only because I haven't stumped up the $99 for a Verisign ID. I would be able to log in to the Microsoft Server and see the error reports, but to do that requires me to authenticate with a Verisign ID, and at the moment I'm not convinced of the benefits.

Quote:

When it next happens is there any information you would like?

I think there's an option on those things to actually show some useful information? That might help. But I suspect it won't be very helpful anyway, and it's probably crashing in the Telerik code.

Quote:

Are you able to replicate this yourself?

I'll have a go; but I've never run C2 for very long at a time. And at the moment it's a pain for me to do that, as I seem to have got C2 into a state where it causes Virtual VP to lock up, and running my Fine Offset station (which is what I'd hoped to use for testing) causes my VP2 to lose connection with the sensors. Both of these screw up my real data. I need to resolve one or both of these problems before I can make much more progress with C2.

gemini06720 · **Posted:** Sun Oct 04, 2009 10:16 am

Steve, as a temporary solution to find out what might be happening between VirtualVP and Cumulus 2, may I suggest that you also run VPLive (at the same time as Cumulus 2) - this way, if weather data appear on the VPLive screen then you know that the data is being imported correctly by VirtualVP and passed on to its ports.

steve · **Posted:** Sun Oct 04, 2009 10:32 am

I don't understand why I need VPLive to tell me that Virtual VP has locked up when all I have to do is look at Virtual VP and see that it has locked up?

gemini06720 · **Posted:** Sun Oct 04, 2009 10:53 am

Steve, it might be because in the 2 years I have been using VirtualVP I have never seen VirtualVP locking on both computers I have been using VirtualVP on - on one computer, VirtualVP has been providing reliably weather information to 4 weather programs and on the other computer, VirtualVP has been providing reliably weather information to both version of Cumulus.

So, I cannot understand how or why VirtualVP can/could/would lock up!

steve · **Posted:** Sun Oct 04, 2009 11:11 am

Well, lock up it did. I'm not making it up

I have (did have) C1 and VVP running on my server, and C2 running on my desktop PC, talking to VVP via TCP/IP (a facility I have added in the latest code). I ran C2 for a while, closed it down, and went away. Later, I looked at the server, and VVP wasn't responding, the C1 data had 'flat-lined' from about the point where I ran C2, and I had to use task manager to kill VVP.

At some point I will have to find some time to investigate further, but at the moment other things are taking priority. My chimney, for one thing

gemini06720 · **Posted:** Sun Oct 04, 2009 12:41 pm

Steve, just out of curiosity, not that I have a solution for you, what type of computer was being used (such as the CPU).

As I wrote previously, VirtualVP is running full time on an Intel Pentium 4 processor (the weather computer with about a half dozen weather related programs running simultaneously) and part time on my development computer, now an Intel Core 2 Quad processor.

What I am getting at, is that more than just VirtualVP might have been locked up and closing VirtualVP might have stopped an chain of events...

Chimney problems, you wrote... They are among the worst... And with those fall and winter rains coming quickly... I feel bad for your...

RayProudfoot · **Posted:** Sun Oct 04, 2009 12:54 pm

steve wrote:

I think there's an option on those things to actually show some useful information? That might help. But I suspect it won't be very helpful anyway, and it's probably crashing in the Telerik code.

I'll send some screenshots. That's the best I can do as I can't capture the text.

steve wrote:

I'll have a go; but I've never run C2 for very long at a time. And at the moment it's a pain for me to do that, as I seem to have got C2 into a state where it causes Virtual VP to lock up, and running my Fine Offset station (which is what I'd hoped to use for testing) causes my VP2 to lose connection with the sensors. Both of these screw up my real data. I need to resolve one or both of these problems before I can make much more progress with C2.

I know it won't be any comfort but I'm running VPP on a netbook with an Atom processor and 1Gb of RAM so muscle isn't your problem. You probably know this but start with a basic setup of VPP + C1 and then add one process at a time until the lockup occurs. Grandmother + eggs + suck springs to mind.

Sounds like yesterday's storm did you no favours. Hope you get a couple of quiet days to sort it out.

steve · **Posted:** Sun Oct 04, 2009 1:53 pm

The server is a 3.4Ghz P4 with 2GB RAM, running Windows Home Server. I'll try just running C2 with VVP for a while to see if I can reproduce this C2 crash (or, indeed, the VVP lock up).

The chimney problem is just that I'm fitting a liner and a new stove, and with it being an old house, and of course having bodges from a previous owner, it's proving to be much more work and much more complicated than I had hoped for.

steve · **Posted:** Sun Oct 04, 2009 2:04 pm

Actually, I may know why the closing the gauges window causes a crash. Well, more precisely, I may know what it's doing that leads to a crash, but I don't understand why it crashes. If that makes sense. Anyway, I'll change what it does when the window closes in the next build.

RayProudfoot · **Posted:** Sun Oct 04, 2009 2:07 pm

steve wrote:

The server is a 3.4Ghz P4 with 2MB RAM, running Windows Home Server. I'll try just running C2 with VVP for a while to see if I can reproduce this C2 crash (or, indeed, the VVP lock up).

The computer equivalent of Arnold Schwartznegger!

The VPP one should be your priority. It's hardly brought any attention to itself here. Good luck!

steve wrote:

The chimney problem is just that I'm fitting a liner and a new stove, and with it being an old house, and of course having bodges from a previous owner, it's proving to be much more work and much more complicated than I had hoped for.

B&Q is filled with those 'experts' every weekend!

RayProudfoot · **Posted:** Sun Oct 04, 2009 2:09 pm

steve wrote:

Actually, I may know why the closing the gauges window causes a crash. Well, more precisely, I may know what it's doing that leads to a crash, but I don't understand why it crashes. If that makes sense. Anyway, I'll change what it does when the window closes in the next build.

Makes sense.

It doesn't happen every time. Only when it's been opened for a while. Anyway, sounds like you're on top of it so I look forward to the next build.

	It is currently Fri May 24, 2013 10:59 pm
Please click here before posting. Help me to help you!
Useful Links: Cumulus FAQ • Enhancement requests • Wiki (documentation)
Please put your approximate location into your profile
Add your web site to the Cumulus user map
Vantage Pro2 users with firmware 3.00 should upgrade to fw 3.12 and Cumulus 1.9.4
Latest Cumulus release v1.9.3 (build 1059) - Feb 09 2013 Latest Cumulus beta v1.9.4 build 1078 - May 24 2013 --> Latest Cumulus Realtime v1.0.0.5 - Sep 05 2009

Sandaysoft

Closing gauges display causes C2 to crash

Who is online