id	summary	reporter	owner	description	type	status	priority	component	version	resolution	keywords	cc
218	Technical Support: High RAM usage/data drop issues and mountpoint relay failures in BNC 2.13.2+	altmb297@…	stuerze	"Dear BKG BNC Support Team,
We are currently encountering two critical issues after upgrading from BNC version 2.13.1, and we would appreciate your guidance or any suggestions you can provide.
**Environment Details:**
**OS / Environment:** Ubuntu 24.04 running inside Docker containers.
**Execution:** We run BNC in no-window mode using the -nw option (generally launched as /opt/bnc-[version] -nw -conf BNC.ini).
**Working Version:** 2.13.1 (and v2.13.2 for the relay feature)
**Problematic Versions:** 2.13.2 & 2.13.4 (RAM issue) / 2.13.4 (Relay issue)
**Server Specs:** Tested across multiple environments, including a 256 GB RAM / HDD setup.

**Issue 1:** High RAM Usage and Data Drops (v2.13.2 & v2.13.4)
When running BNC 2.13.2 and 2.13.4, the application begins to ignore incoming data, and its RAM usage climbs exponentially—reaching up to 100 GB on our 256 GB machine.
Here is some information regarding this:
We do not experience this issue in Version 2.13.1 under the exact same load.
We initially thought this might be related to HDD disks not handling the I/O load, but version 2.13.1 works perfectly with the exact same HDD setup.
We have replicated this RAM issue across different machines running the same Ubuntu 24.04 Docker setup.
While it happens consistently with a large number of mountpoints, we have also occasionally experienced it when testing with a low number of mountpoints.
The issue appears significantly more likely to happen if the casters are accessed via a secure port (e.g., 443, 2102).
Has there been a change in how BNC handles internal queuing, threading, or secure port connections in no-window mode within these newer versions that could account for this memory accumulation?

**Issue 2:** Mountpoint ""Relay"" Feature in v2.13.4
In version 2.13.1, we successfully used BNC to relay a specific mountpoint to an internal service. Our configuration relied primarily on the following options:
mountPoints
casterPort
miscMount
miscPort
This setup allowed a downstream service (for example, running str2str -in tcpcli://my_server:port/MOUNTPOINT) to successfully listen to and consume the relayed mountpoint.
As of version 2.13.4, this functionality has stopped working for us.
The incoming data works and can be seen in a file if the outFile option is used
Could you please indicate if there was a change to how miscPort / casterPort broadcasting is handled in the latest release, or if we need to adjust our configuration format to achieve the same result?
We would be happy to provide our configuration files (BNC.ini) or bnc log outputs if that helps diagnose the issue. Looking forward to your insights.

Many thanks for the help in advance,

Best regards,"	defect	new	normal	BNC