{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/node/issues/8074","repository_url":"https://api.github.com/repos/nodejs/node","labels_url":"https://api.github.com/repos/nodejs/node/issues/8074/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/node/issues/8074/comments","events_url":"https://api.github.com/repos/nodejs/node/issues/8074/events","html_url":"https://github.com/nodejs/node/issues/8074","id":170760309,"number":8074,"title":"segfault on node v6.3.1 on Ubuntu 14.04.4","user":{"login":"uhoh-itsmaciek","id":159100,"avatar_url":"https://avatars.githubusercontent.com/u/159100?v=3","gravatar_id":"","url":"https://api.github.com/users/uhoh-itsmaciek","html_url":"https://github.com/uhoh-itsmaciek","followers_url":"https://api.github.com/users/uhoh-itsmaciek/followers","following_url":"https://api.github.com/users/uhoh-itsmaciek/following{/other_user}","gists_url":"https://api.github.com/users/uhoh-itsmaciek/gists{/gist_id}","starred_url":"https://api.github.com/users/uhoh-itsmaciek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/uhoh-itsmaciek/subscriptions","organizations_url":"https://api.github.com/users/uhoh-itsmaciek/orgs","repos_url":"https://api.github.com/users/uhoh-itsmaciek/repos","events_url":"https://api.github.com/users/uhoh-itsmaciek/events{/privacy}","received_events_url":"https://api.github.com/users/uhoh-itsmaciek/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nodejs/node/labels/c++","name":"c++","color":"e11d21"},{"url":"https://api.github.com/repos/nodejs/node/labels/tls","name":"tls","color":"fad8c7"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2016-08-11T22:15:51Z","updated_at":"2016-08-12T21:00:07Z","closed_at":null,"body":"<!--\r\nThank you for reporting an issue.\r\nPlease fill in as much of the template below as you're able.\r\n\r\nVersion: output of `node -v`\r\nPlatform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)\r\nSubsystem: if known, please specify affected core module name\r\n\r\nIf possible, please provide code that demonstrates the problem, keeping it as\r\nsimple and free of external dependencies as you are able.\r\n-->\r\n\r\n* **Version**: v6.3.1\r\n* **Platform**: Ubuntu 14.04.4 LTS (Heroku)\r\n* **Subsystem**: ?\r\n\r\n<!-- Enter your issue details below this comment. -->\r\n\r\nHello,\r\n\r\nI seem to be able to fairly reliably (maybe 50% of the time) reproduce a segfault with node v6.3.1 in my express application. I'm not using any native modules (except for `segfault-handler` to get the trace output below, and the error of course also occurs without `segfault-handler`).\r\n\r\nThis is the output I get:\r\n\r\n```\r\nPID 17 received SIGSEGV for address: 0x753760f\r\n/app/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x1b04)[0x7f1fd8283b04]\r\n/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f1fdce8b330]\r\nnode(_ZN4node7TLSWrap7IsAliveEv+0x16)[0x1026586]\r\nnode(_ZN4node10StreamBase5GetFDINS_7TLSWrapEEEvN2v85LocalINS3_6StringEEERKNS3_20PropertyCallbackInfoINS3_5ValueEEE+0x92)[0x102b192]\r\nnode(_ZN2v88internal25PropertyCallbackArguments4CallEPFvNS_5LocalINS_4NameEEERKNS_20PropertyCallbackInfoINS_5ValueEEEES4_+0xd2)[0x981c12]\r\nnode(_ZN2v88internal6Object23GetPropertyWithAccessorEPNS0_14LookupIteratorE+0x1bd)[0xd16c1d]\r\nnode(_ZN2v88internal6Object11GetPropertyEPNS0_14LookupIteratorE+0x13b)[0xd51c2b]\r\nnode(_ZN2v88internal6LoadIC4LoadENS0_6HandleINS0_6ObjectEEENS2_INS0_4NameEEE+0x145)[0xcbc1c5]\r\nnode[0xcbcfdc]\r\nnode(_ZN2v88internal24Runtime_KeyedLoadIC_MissEiPPNS0_6ObjectEPNS0_7IsolateE+0x112)[0xcbfef2]\r\n[0x1367f3c0961b]\r\n```\r\n\r\nThe error seems to happen right after I send a message to a client via socket.io, but the message itself seems to send correctly (that is, I see a log line after the `.emit`).\r\n\r\nI looked at the other open issues mentioning segfaults, but I did not see anything relevant.\r\n\r\nAny ideas?"},"comment":{"url":"https://api.github.com/repos/nodejs/node/issues/comments/239558469","html_url":"https://github.com/nodejs/node/issues/8074#issuecomment-239558469","issue_url":"https://api.github.com/repos/nodejs/node/issues/8074","id":239558469,"user":{"login":"uhoh-itsmaciek","id":159100,"avatar_url":"https://avatars.githubusercontent.com/u/159100?v=3","gravatar_id":"","url":"https://api.github.com/users/uhoh-itsmaciek","html_url":"https://github.com/uhoh-itsmaciek","followers_url":"https://api.github.com/users/uhoh-itsmaciek/followers","following_url":"https://api.github.com/users/uhoh-itsmaciek/following{/other_user}","gists_url":"https://api.github.com/users/uhoh-itsmaciek/gists{/gist_id}","starred_url":"https://api.github.com/users/uhoh-itsmaciek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/uhoh-itsmaciek/subscriptions","organizations_url":"https://api.github.com/users/uhoh-itsmaciek/orgs","repos_url":"https://api.github.com/users/uhoh-itsmaciek/repos","events_url":"https://api.github.com/users/uhoh-itsmaciek/events{/privacy}","received_events_url":"https://api.github.com/users/uhoh-itsmaciek/received_events","type":"User","site_admin":false},"created_at":"2016-08-12T21:00:07Z","updated_at":"2016-08-12T21:00:07Z","body":"A colleague suggested that this seems similar to [an issue fixed recently in Postgres](https://github.com/postgres/postgres/commit/7c7d4fddab82dc756d8caa67b1b31fcdde355aab)--we looked at the node code you linked briefly @addaleax and it's not obviously the same issue, but perhaps it's related? In both cases, two independent clients are managing their own TLS connections in the same process, and at least in the Postgres case, the OpenSSL API made it difficult to do this safely."}}
{"actor":{"display_login":"uhoh-itsmaciek"}}