John Huff

I actually don't have a use case for changing heapmax during runtime. I've been developing an HTTP API for semi-remote (i.e. using terrestrial Internet) ION node management. I just happened to stumble across this as I was testing my API.

Note that ltpdb->maxAcqInHeap is used elsewhere for allocating buffers such as in ltpdeliv. So if you increase the size of any session buffers while ltpdeliv is still running, the ltpdeliv buffer will overflow. This should also be addressed. Something simple you could do would be to define a maximum allowed value for maxAcqInHeap such as 64KB, and allocate a buffer of that size in ltpdeliv. This is ineffcient but ensures that ltpdeliv always has a big enough buffer.

LTP heap buffer overflow

Primary block is mutated due to incomplete CRC support

Actually, the handleAdminBundles function does correctly handle the SIGTERM signal, ending the BpSAP recvSemaphore. However, handleAdminBundles doesn't close the BpSAP on exit.

scheme adminep daemons leak psm memory on stop

this was from me btw, forgot to log in

Yes, my understanding is that it should be newRoute. newRoute was correctly having toNodeNbr and fromTime set in computeRoute, making this bug harder to detect. Computing a spur route shouldn't have any effect on the route used to compute it.