billt-hlit

I've been seeing a memory leak of the same order of magnitude (1.25 MB/s in my case) that @amiller-isp reported. I'm using the gstreamer SRT sink plug-in rather than srt_transmit....

The process gets killed for using up too much memory well before the socket gets closed. It only takes a few minutes before the process gets killed for using too...

I'm using libavahi's compatibility library. I'm using the BBC registry VM image that they published early this year -- I tried the vagrant image but kept being stymied fairly late...

My machine is 64-bit as well. In any event, I'm still in the duct tape and bailing wire stage, so I don't need to pursue this test any further in...

Hi, Gareth, The machine's hostname is "hobbes", but I'm setting it to "D13_04204" (or somesuch) on the command line. Also, I realized I have a 32-bit chroot lying around. I...

That fixes it! I'm only setting the host name for testing purposes anyhow, so this problem shouldn't impact my work in the long term. Thanks!

I can't get attachments to work, so I'm going to have to paste them into comments. This is the patch I used. ``` diff --git Development/nmos-cpp-node/main.cpp Development/nmos-cpp-node/main.cpp index 33cf1f6..85a377c 100644...

This is the node's output ``` $ ./nmos-cpp-node '{"logging_level":-24, "seed_id": "8b2caf6f-5850-509f-8c47-c009ccb8d90d", "hostname": "D13-04284"}' < 1port 2018-08-03 20:15:41.646: info: 140119400593600: Starting nmos-cpp node 2018-08-03 20:15:41.649: info: 140119400593600: Process ID: 91456 2018-08-03...

This is the registry's output (no command-line options): ``` 2018-08-03 20:16:21.539: info: 139976104589056: Registration requested for node: 85f7cadf-32bb-5c3d-97d4-443daa2d42ae 2018-08-03 20:16:21.540: more info: 139976104589056: At 1533327381:539461510, the registry contains 2 resources...

OK, I see. Would it make sense for modify_resource to update the version rather than relying on the modifier function to do so? Thanks.