Investigate upstream Vibe.d issue: Handle leak #1136
Comments
Geod24
added
the
type-bug
|
quick update on the issue:
2.1 Reproduce issue of streamSocket void main()
{
auto settings = new HTTPServerSettings;
settings.bindAddresses = ["127.0.0.1"];
settings.port = 8080;
auto router = new URLRouter;
router.get("/weather", &weather);
HTTPListener httpListener = listenHTTP(settings, router);
runApplication();
httpListener.stopListening;
}2.1.1 start up the server above 2.2 Reproduce issue of streamSocket 2.2.1 2.2.2 you will see some connection attempts like this: if you let the sockets connect to hosts successfully, then they are cleaned up after CTRL+C it doesn't seem straightforward to fix either 2.1 or 2.2 without delving into vibe.d code very heavily. Vibe.d does register signal handlers, so it does catch SIGINT and SIGTERM, and attempts to clean up after itself, it just doesn't succeed in it. |
|
and easier way to reproduce 2.2 is this: void main()
{
runTask({
requestHTTP("http://www.index.hu",
(scope req) {
req.method = HTTPMethod.GET;
},
(scope res) {
logInfo("Response: %s", res.bodyReader.readAllUTF8());
}
);
requestHTTP("http://192.168.1.42:2828", // make sure this is not reachable by ping
(scope req) {
req.method = HTTPMethod.GET;
},
(scope res) {
logInfo("Response: %s", res.bodyReader.readAllUTF8());
}
);
});
runApplication();
}compile with "versions": [ "VibeHighEventPriority" ]
|
Manually call `stopListening()` on the `HTTPListener` after node shutdown to avoid leaking handles. Fixes bosagora#1136
bpalaggi
added
the
C. Network Communication
We're currently seeing the following output in the integration tests:
It would be good to take a look into the issue. Some upstream discussion: vibe-d/vibe.d#2245
The text was updated successfully, but these errors were encountered: