-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
connection stay in CLOSED state #11
Comments
How can I reproduce it? ctrl-c ? |
What I did was just opening up another console and connecting to the server with nc:
after ctrl+c the nc process here is what lsof reports:
and the mruby process is still printing happilly "helloworld" every second. I am ruby it on Mac OS X so it may also be an issue with the master branch of libuv under Mac OS X xD |
I added bits code for GC. but mruby-uv need to call |
During my tests the rescue block wasn't even executed since no exception was raised, it almost looks like something is missing to cleanup the closed socket. Do you experience the same behavior I described ? If not can you give me the revision of your libuv install so I can check with it ? |
In latest version, It seems occur SIGPIPE if closes nc connection. |
I just tried with latest version of your gem and mruby with libuv 0.9.4, same issue. What did you meant by latest version ? latest version of your gem ? |
libuv changed |
done. |
It compiles but sadly I still have the same behavior with netcat :( |
It should occur SIGPIPE. latest mruby-uv/example/tcp-server.rb handles SIGPIPEs. |
I tested the gem with the master branch of mruby and master of libuv (I first tested with the latest stable release but uv_run2 was only added after), when I run the tcp-server example it works fine except that it never detects CLOSED connection (the puts/write timer continue and lsof reports the socket as CLOSED).
Since it may be an issue with the master branch of libuv I was wondering which revision you tested this gem with.
I did some minor changes to compile on Mac OS X but I am confident they are not causing the issue since they concern only the building part, I will send you a pull request but I want to make sure everything works fine before that.
The text was updated successfully, but these errors were encountered: