Strange behaviors possibly caused by memory leaks (and more)

Community Playground General Discussions
1

Hi all! I’m on UI5 (1.5.622 ) running on Vera3.

I’ve struggeled the past few days with some luup-code not working as expected. I believe I experienced a lot of strange and unexpected behaviors so I did my first debug session. I found several lines in LuaUPnP.log indicating memory leaks. I deleted a PLEG device that I’ve been working on recently and things started to look a bit better. I still may have some problems to solve before I can start to make any further development.

Here are the log entries ordered by time that I find suspicious

[ol][li]03/15/14 15:40:21.203 GetSunriseSunset error#1 sunrise: 1394774769/2014-03-14 06:26:09 sunset: 1394817171/2014-03-14 18:12:51 midnight: 1394838000/9611972 <0x2b651000>[/li]
[li]03/15/14 15:40:23.254 luup_require can’t find veraUserTemplateDefinitions LEAK this:184320 start:184320 to 0xce7000 <0x2bf85680>[/li]
[li] 03/15/14 15:40:46.101 luup_log:7: InitD: 1394860845 : 1394894446 : 1394903700 LEAK this:8192 start:1294336 to 0xdf6000 <0x2cb85680>[/li]
[li]03/15/14 15:42:14.622 LEAK this:4096 start:1298432 to 0xdf7000 <0x2bd85680>[/li][/ol]

(My device no 7 was the “Day or Night” -plugin, Version: 1.8, I deleted it now.)

About luup_require can’t find veraUserTemplateDefinitions it seems to be related to VeraAlerts plugin so I’ve posted that question in the proper thread already.

Any ideas how I can solve my problems? What are normally causing memory leak problems on my Vera?

2

On line 3. I believe that luup_log:7: is referring to the syslog local logging facility 7 which is supposed to be network news, but is very commonly used as a local catchall facility. My point is that it has nothing to do with node 7.

Line 4. Job ID 7 is irrelevant. But, node 11 _4 in 1 sensor (motion) might have an issue. It is not uncommon to see this log entry from time to time, but if it happens frequently, you may want to exclude and include the device. This will reset it to defaults and often resolves such errors.

Be aware that it is unlikely that you will eliminate all memory leak messages from your logs. Don’t let them steal your focus away from the more likely issue that your Luup simply isn’t yet right, despite your expectations.

3

I do not believe the LEAK messages are synchronized with the source of the leak.
There are internal messages that MCV added for debugging … and can be found in many places in the log.
MCV does leak memory … and if your memory is tight … you will be restarting quicker.
I suggest you reduce the total number of plugin devices you have installed.