~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@not_bob
@orignal
@postman
@zzz
%Liorar
+FreefallHeavens
+RTP
+Xeha
+bak83
+cancername
+cumlord
+hk
+profetikla
+uop23ip
Arch
DeltaOreo
FreeRider
Irc2PGuest28511
Irc2PGuest64530
Irc2PGuest75862
Meow
Nausicaa
Onn4l7h
Onn4|7h
Over1
acetone_
anon4
anu
boonst
enoxa
mareki2pb
plap
poriori_
shiver_1
simprelay
solidx66
u5657
weko_
darius
Hi, i'm here again to cause different trouble, still re i2p snark
darius
i'm not sure that the files are closed properly at the java level
darius
ie. specifically the files that are being seeded via i2psnark, the pointer that java creates to them appears to be remaining "open" after even i2psnark is turned off from the 127.0.0.1:7657/configwebapps page
darius
I may not be a ble to stay online long
dr|z3d
if you've got more info you can share, darius, maybe consider filing a report on git.idk.i2p/i2p-hackers/i2p.i2p/-/issues
darius
theres not much else to share, I seem to have spotted it doing something I've done b4 and if this bug(?) wasn't new I'd have seen it then. SO I'm guessing it new given some TLC was given to i2psnark in the update
darius
I'm suspecting that every time a new connection is made that a new pointer is created and they are never closed.
darius
So we might be ending up with thousands of open pointers to a file,
darius
They are probably harmless
darius
I seem to need to find a way to get rid of them though, because they are stopping me from doing things.
darius
must go
snex
losf will tell you if there are open file handles
darius
lsof yes :) luv ur works as always
darius
every1
darius
mus go