{"action":"created","issue":{"url":"https://api.github.com/repos/ChrisTruncer/EyeWitness/issues/125","labels_url":"https://api.github.com/repos/ChrisTruncer/EyeWitness/issues/125/labels{/name}","comments_url":"https://api.github.com/repos/ChrisTruncer/EyeWitness/issues/125/comments","events_url":"https://api.github.com/repos/ChrisTruncer/EyeWitness/issues/125/events","html_url":"https://github.com/ChrisTruncer/EyeWitness/issues/125","id":69002916,"number":125,"title":"Segmentation Fault Constant","user":{"login":"ebrinkster","id":616045,"avatar_url":"https://avatars.githubusercontent.com/u/616045?v=3","gravatar_id":"","url":"https://api.github.com/users/ebrinkster","html_url":"https://github.com/ebrinkster","followers_url":"https://api.github.com/users/ebrinkster/followers","following_url":"https://api.github.com/users/ebrinkster/following{/other_user}","gists_url":"https://api.github.com/users/ebrinkster/gists{/gist_id}","starred_url":"https://api.github.com/users/ebrinkster/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ebrinkster/subscriptions","organizations_url":"https://api.github.com/users/ebrinkster/orgs","repos_url":"https://api.github.com/users/ebrinkster/repos","events_url":"https://api.github.com/users/ebrinkster/events{/privacy}","received_events_url":"https://api.github.com/users/ebrinkster/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-04-16T20:26:10Z","updated_at":"2015-04-22T18:31:44Z","closed_at":null,"body":"I'm noticing lots of segmentation fault's when scanning large ranges that contain 500+ or more targets.  Is it possible to provide the capability to start off a scan when the segmentation fault occurs on a previously started (but stopped abruptly) scan?"},"comment":{"url":"https://api.github.com/repos/ChrisTruncer/EyeWitness/issues/comments/95293507","html_url":"https://github.com/ChrisTruncer/EyeWitness/issues/125#issuecomment-95293507","issue_url":"https://api.github.com/repos/ChrisTruncer/EyeWitness/issues/125","id":95293507,"user":{"login":"ChrisTruncer","id":1674822,"avatar_url":"https://avatars.githubusercontent.com/u/1674822?v=3","gravatar_id":"","url":"https://api.github.com/users/ChrisTruncer","html_url":"https://github.com/ChrisTruncer","followers_url":"https://api.github.com/users/ChrisTruncer/followers","following_url":"https://api.github.com/users/ChrisTruncer/following{/other_user}","gists_url":"https://api.github.com/users/ChrisTruncer/gists{/gist_id}","starred_url":"https://api.github.com/users/ChrisTruncer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ChrisTruncer/subscriptions","organizations_url":"https://api.github.com/users/ChrisTruncer/orgs","repos_url":"https://api.github.com/users/ChrisTruncer/repos","events_url":"https://api.github.com/users/ChrisTruncer/events{/privacy}","received_events_url":"https://api.github.com/users/ChrisTruncer/received_events","type":"User","site_admin":false},"created_at":"2015-04-22T18:31:44Z","updated_at":"2015-04-22T18:31:44Z","body":"Ok, definitely let me know with the beta and using selenium (with the --web option).  I keep checking the ghost repo, and it looks like their last commit was a while ago, so I'm a little concerned that dev has stopped on it in a semi-functional state, but still has obviously errors.\r\n\r\nIf that's the case, I'll probably end up removing ghost to stop that issue, and as much as I tried to stay away from it, I might add in phantomjs so people have a second option."}}