On Monday, 15 January 2024 at 22:19:56 UTC, Steven Schveighoffer
wrote:
You may have to do the same thing I did with redis:
https://github.com/vibe-d/vibe.d/pull/2372
Good luck! I would also say, I don't know why Windows doesn't
do the same trace info debug thing, except that probably
On Monday, 15 January 2024 at 18:40:00 UTC, bomat wrote:
Sorry, I probably should have mentioned I was on Windows.
For testing it under Linux I commented out the call to
`connectMongoDB`, since I don't have it installed there - and
the warning went away.
Interesting, I did not suspect that as
On Monday, 15 January 2024 at 17:45:16 UTC, Steven Schveighoffer
wrote:
Which driver are you using? In the posix driver, it should
mention (and use) the debug flag `EventCoreLeakTrace`.
On Monday, 15 January 2024 at 17:24:40 UTC, bomat wrote:
On Sunday, 14 January 2024 at 20:36:44 UTC, Steven
Schveighoffer wrote:
There should be a version you can enable that tells you where
that socket handle was allocated. That might give you a
further clue as to why it's not closed when the
On Sunday, 14 January 2024 at 20:36:44 UTC, Steven Schveighoffer
wrote:
There should be a version you can enable that tells you where
that socket handle was allocated. That might give you a further
clue as to why it's not closed when the system shuts down.
I think the program tells you which
On Saturday, 13 January 2024 at 20:49:54 UTC, bomat wrote:
I am still getting this in 2024 and vibe.d 0.9.7:
```
Warning: 1 socket handles leaked at driver shutdown.
```
I was wondering if maybe someone has new info on this...
There should be a version you can enable that tells you where
I am still getting this in 2024 and vibe.d 0.9.7:
```
Warning: 1 socket handles leaked at driver shutdown.
```
I was wondering if maybe someone has new info on this...
On Friday, 1 January 2021 at 22:07:28 UTC, Selim Ozel wrote:
[2] https://github.com/SelimOzel/vibe_noLeaks
I don't see anything abnormal in this code though. Will trying it
later today myself.
Could you show the actual socket code causing that leak?
On Tuesday, 5 January 2021 at 21:12:01 UTC, Selim Ozel wrote:
On Monday, 4 January 2021 at 17:17:10 UTC, Steven Schveighoffer
wrote:
On 1/2/21 12:52 PM, Selim Ozel wrote:
After logging into to 127.0.0.1 for a single time in my
browser, if I do a ctrl+c it still leaks two socket handles.
On Monday, 4 January 2021 at 17:17:10 UTC, Steven Schveighoffer
wrote:
On 1/2/21 12:52 PM, Selim Ozel wrote:
After logging into to 127.0.0.1 for a single time in my
browser, if I do a ctrl+c it still leaks two socket handles.
With connection Windows 10:
Running .\vibe_noleaks.exe
On Sunday, 3 January 2021 at 23:53:54 UTC, aberba wrote:
On Friday, 1 January 2021 at 22:07:28 UTC, Selim Ozel wrote:
I created the simplest possible example as explained by the
Vibe-D community in [1]. The exact source code of what I run
is in [2].
On Windows I get a socket handle leak
On 1/4/21 12:17 PM, Steven Schveighoffer wrote:
If you want a few seconds
*wait* a few seconds
-Steve
On 1/3/21 6:53 PM, aberba wrote:
On Friday, 1 January 2021 at 22:07:28 UTC, Selim Ozel wrote:
I created the simplest possible example as explained by the Vibe-D
community in [1]. The exact source code of what I run is in [2].
On Windows I get a socket handle leak warning on shutdown with
On 1/2/21 12:52 PM, Selim Ozel wrote:
After logging into to 127.0.0.1 for a single time in my browser, if I do
a ctrl+c it still leaks two socket handles.
With connection Windows 10:
Running .\vibe_noleaks.exe
[main() INF] Listening for requests on http://[::1]:8080/
[main() INF]
On Friday, 1 January 2021 at 22:07:28 UTC, Selim Ozel wrote:
I created the simplest possible example as explained by the
Vibe-D community in [1]. The exact source code of what I run is
in [2].
On Windows I get a socket handle leak warning on shutdown with
crtl+c from terminal after running
On Friday, 1 January 2021 at 22:07:28 UTC, Selim Ozel wrote:
I created the simplest possible example as explained by the
Vibe-D community in [1]. The exact source code of what I run is
in [2].
On Windows I get a socket handle leak warning on shutdown with
crtl+c from terminal after running
On Saturday, 2 January 2021 at 00:28:43 UTC, Steven Schveighoffer
wrote:
On 1/1/21 5:07 PM, Selim Ozel wrote:
I created the simplest possible example as explained by the
Vibe-D community in [1]. The exact source code of what I run
is in [2].
On Windows I get a socket handle leak warning on
On 1/1/21 5:07 PM, Selim Ozel wrote:
I created the simplest possible example as explained by the Vibe-D
community in [1]. The exact source code of what I run is in [2].
On Windows I get a socket handle leak warning on shutdown with crtl+c
from terminal after running the executable.
I created the simplest possible example as explained by the
Vibe-D community in [1]. The exact source code of what I run is
in [2].
On Windows I get a socket handle leak warning on shutdown with
crtl+c from terminal after running the executable.
[main() INF] Listening for requests on
19 matches
Mail list logo
