Segfault on Shutdown of Octave
Description
On shutdown of octave, the caosdb module produces a segfault. Apparently this has something to do with the logging frame work (boost log) and the grpc memory management (via so-called 'arenas').
Fixes have been attempted, but the root of the problem is still unknown and no fix has been found yet.
The segfault happens during the destruction of the arena and/or the loggers after the main function of octave has been finished. Octave will return a non-zero exit code. It is possible that the problem affects the shutdown of octave. However, no actual effects of that have been observed yet.
Work-around
Turn off logging
A work-around which works in many cases (though not all) is turning off the logging by setting the log-level to "off" in the client configuration:
{
"connections": {
...
},
"logging": {
"level": "off"
}
}