Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
3.2.1
-
None
-
1
Description
When supplying a custom tracer the lcbtrace destructor is not initialized here. This leads to an uninitialized read when lcbtrace_destroy is called on cluster close.
const couchbase = require("../couchnode");
|
|
class TestTracer {
|
constructor() {
|
}
|
|
requestSpan(name, parent) {
|
return new TestSpan();
|
}
|
}
|
|
class TestSpan {
|
constructor(name, parent) {
|
}
|
|
addTag(key, value) {
|
}
|
|
end() {
|
}
|
}
|
|
async function main() {
|
const cluster = await couchbase.connect("couchbase://localhost", {
|
username: "Administrator",
|
password: "password",
|
tracer: new TestTracer(),
|
});
|
console.log("connected")
|
await cluster.close()
|
}
|
|
main();
|
|
node index.js
connected
zsh: segmentation fault node index.js
Attachments
Issue Links
- relates to
-
CCBC-1479 lcbtrace_new LCBTRACE_F_EXTERNAL does not zero-initialize
- Resolved