{"action":"created","issue":{"url":"https://api.github.com/repos/joyent/node/issues/25570","labels_url":"https://api.github.com/repos/joyent/node/issues/25570/labels{/name}","comments_url":"https://api.github.com/repos/joyent/node/issues/25570/comments","events_url":"https://api.github.com/repos/joyent/node/issues/25570/events","html_url":"https://github.com/joyent/node/issues/25570","id":90713565,"number":25570,"title":"SIGSEGV when polling for changes on v0.12.4","user":{"login":"ansman","id":102883,"avatar_url":"https://avatars.githubusercontent.com/u/102883?v=3","gravatar_id":"","url":"https://api.github.com/users/ansman","html_url":"https://github.com/ansman","followers_url":"https://api.github.com/users/ansman/followers","following_url":"https://api.github.com/users/ansman/following{/other_user}","gists_url":"https://api.github.com/users/ansman/gists{/gist_id}","starred_url":"https://api.github.com/users/ansman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ansman/subscriptions","organizations_url":"https://api.github.com/users/ansman/orgs","repos_url":"https://api.github.com/users/ansman/repos","events_url":"https://api.github.com/users/ansman/events{/privacy}","received_events_url":"https://api.github.com/users/ansman/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/joyent/node/labels/needs-more-info","name":"needs-more-info","color":"eb6420"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-06-24T15:41:25Z","updated_at":"2015-06-24T22:13:43Z","closed_at":null,"body":"This happens frequently when I try to monitor the filesystem for changes while adding, removing or changing files.\r\n\r\nI'm running OS X 10.10.3\r\nIt might be causes by a 3rd party module but I'm not sure which one it that case.\r\n\r\n```\r\nPID 95295 received SIGSEGV for address: 0x10\r\n0   segfault-handler.node               0x0000000100afb91a _ZL16segfault_handleriP9__siginfoPv + 282\r\n1   libsystem_platform.dylib            0x00007fff94210f1a _sigtramp + 26\r\n2   ???                                 0x00000a4a03f84281 0x0 + 11313010459265\r\n3   node                                0x0000000100494301 uv__async_event + 65\r\n4   node                                0x0000000100494484 uv__async_io + 136\r\n5   node                                0x00000001004a20e3 uv__io_poll + 1579\r\n6   node                                0x00000001004948e9 uv_run + 276\r\n7   node                                0x0000000100435a48 _ZN4node5StartEiPPc + 344\r\n8   node                                0x0000000100002134 start + 52\r\n```"},"comment":{"url":"https://api.github.com/repos/joyent/node/issues/comments/115026154","html_url":"https://github.com/joyent/node/issues/25570#issuecomment-115026154","issue_url":"https://api.github.com/repos/joyent/node/issues/25570","id":115026154,"user":{"login":"misterdjules","id":811047,"avatar_url":"https://avatars.githubusercontent.com/u/811047?v=3","gravatar_id":"","url":"https://api.github.com/users/misterdjules","html_url":"https://github.com/misterdjules","followers_url":"https://api.github.com/users/misterdjules/followers","following_url":"https://api.github.com/users/misterdjules/following{/other_user}","gists_url":"https://api.github.com/users/misterdjules/gists{/gist_id}","starred_url":"https://api.github.com/users/misterdjules/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/misterdjules/subscriptions","organizations_url":"https://api.github.com/users/misterdjules/orgs","repos_url":"https://api.github.com/users/misterdjules/repos","events_url":"https://api.github.com/users/misterdjules/events{/privacy}","received_events_url":"https://api.github.com/users/misterdjules/received_events","type":"User","site_admin":false},"created_at":"2015-06-24T22:13:43Z","updated_at":"2015-06-24T22:13:43Z","body":"@ansman Being able to reproduce the issue in some way would be key to identify if that's an issue with Node.js' core or with one of the dependencies you're using. Do you have some time to try to come up with some code that only watches files and trigger that crash?\r\n\r\nOtherwise, maybe reporting this issue in gulp-watch would be a good start?"}}