Skip to content

AssertionError crash at ServerResponse.resOnFinish #2639

Description

Running io.js 3.2 installed from source on a centOS 7 machine, here are the logs:
http://pastebin.com/ix0Ke5zS

Activity

  1. added
    httpIssues and PRs related to the http subsystem.
    on Sep 2, 2015
  2. mscdex commented on Sep 2, 2015

    @mscdex
    Contributor

    Did you try with other versions, like io.js 2.5.0?

  3. ghost closed this as completedon Sep 2, 2015
  4. ghost reopened this on Sep 2, 2015
  5. arthurschreiber commented on Sep 15, 2015

    @arthurschreiber

    We see the same error with Node 4.0 on our RHEL 6 machines. We haven't seen this issue with io.js 2.5.0.

  6. arthurschreiber commented on Sep 15, 2015

    @arthurschreiber

    This seems to be related to #1411. @indutny Any idea what's happening here?

    Stacktrace:

    AssertionError: false == true
        at ServerResponse.detachSocket (_http_server.js:144:3)
        at ServerResponse.resOnFinish (_http_server.js:483:11)
        at emitNone (events.js:67:13)
        at ServerResponse.emit (events.js:166:7)
        at finish (_http_outgoing.js:526:10)
        at doNTCallback0 (node.js:407:9)
        at process._tickDomainCallback (node.js:377:13)
    
  7. fasiha commented on Sep 20, 2015

    @fasiha

    I'm running into the same issue with node 4.1.0 using just Express. Looks like socket.io folks are seeing this too: socketio/socket.io#2236 😭 Definitely not RAM: 16 GB here.

  8. fasiha commented on Sep 20, 2015

    @fasiha

    I may have fixed it with an npm update to pull in updated dependencies (instead of just using whatever version was saved when I did npm install X --save who-knows-when).

  9. khoikng commented on Sep 20, 2015

    @khoikng

    I'm running into the same issue with iojs 3.0.0 :( Any update on this?

    @fasiha how are you going with npm update?

  10. 61 remaining items

  11. mareksrom commented on Sep 25, 2015

    @mareksrom

    yeah of course, we can, as I wrote this is only fix, I didn't want to make bigger changes that I think should be done here... I don't know anything about your guidelines and so on, I was just unhappy of node falling down every few minutes and it was a good reason to look a bit under the cover...:)

  12. fasiha commented on Sep 29, 2015

    @fasiha

    @indutny @mareksrom sorry I'm a little unclear on the status of your patches—should we be testing them, or are they both in flux? Apologies for being dense…

    I ask because @arthurschreiber seems to have experienced assertion failure with @indutny's patch.

  13. rvagg commented on Sep 29, 2015

    @rvagg
    Member

    I believe @mareksrom's patch is in the closest state to being merged; either way we'll have a release out this week with a fix in it as it seems like the cause has been fully diagnosed now.

  14. fasiha commented on Sep 29, 2015

    @fasiha

    🎉 so happy! Thanks everyone 🍻

  15. rvagg commented on Oct 5, 2015

    @rvagg
    Member

    Please upgrade to v4.1.2 and confirm that this problem has been resolved.

  16. ahwayakchih commented on Oct 6, 2015

    @ahwayakchih

    Hi, i started noticing problem, searched for info, found this issue, updated to 4.1.2 and now the problem is gone. Thanks!

  17. gesposito commented on Oct 8, 2015

    @gesposito

    It used to crash often while developing on Windows (http-server with a lot of static requests), looks stable now, thanks.

  18. micky2be commented on Oct 14, 2015

    @micky2be

    Thanks

  19. hi54yt commented on Feb 3, 2016

    @hi54yt

    thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    httpIssues and PRs related to the http subsystem.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions