Page 1 of 1

Application crash

Posted: Mon Jul 30, 2012 9:22 pm
by vdoucet
Hi all,
since few weeks if not months my Ubuntu / Domotiga has been running heraticaly. One application crash per day, more or less, without knowing the origin. I finally upgraded Ubuntu to 12.04 and Domotiga to the latest (0.1.208). All seemed quite stable for a few days until today where I was able to have an error message :
"This application has raised an unexpected error and must abort.
[13] Null object.
Main.BroadcastUDP_Error.5869"
I have no idea where that could come from and how to prevent it from happening again.
Thanks in advance.
Vincent

Re: Application crash

Posted: Wed Aug 01, 2012 9:23 am
by Mosibi
Looking at the domotiga code ( http://www.domotiga.nl/projects/domotig ... ain.module ), i see on line 5869 the following:

SELECT CASE hBroadcastEvent.Status.

After this there is a handler for error events, but not for the event you are seeing. As i do not have any experience with the language where Domotiga is written in, i do not know how to exactly read the event you are getting: '[13] Null object.' To me it looks like 'hBroadcastEvent.Status' is set but empty. I think there should be a handler for unknown errors, something like this:

CASE *
Main.WriteDebugLog(("[BroadcastUDP] Unknown error:
hBroadcastEvent.Status"))

Here the author of this can choose to keep the programm running (and log it) or exit (and log it)

Re: Application crash

Posted: Thu Aug 02, 2012 1:37 pm
by RDNZL
I have added a CATCH statement to the latest revision to catch this error.
Thanks for reporting.
Regarding unstable installation; it's hard to see if it's hardware, OS and/or DomotiGa related right now.
If you have more information we can look into that.

Re: Application crash

Posted: Thu Aug 02, 2012 2:44 pm
by RDNZL
What I also noticed is that you have 'Gambas 2.21' in your tagline, please upgrade to 2.24, since older versions of Gambas contain bugs that make it unsuitable for 24/7 operation.

Re: Application crash

Posted: Mon Aug 06, 2012 8:14 am
by uAlex73
@vdoucet: I had the similair problem with the broadcast udp and i was able to reproduce it and this fix should be in the repository soon (the UDP socket will be initialized at the start, not with every broadcast as before).