Weird issue with concurrent requests and event callbacks

[cjroebuck]

Hey @lawnsea, first of all - thanks a lot for SpookyJS.

I'm having an issue when using Spooky on different URLs in parallel. I want to capture a screenshot of urls A, B and C

I set up spooky and listen on the capture.saved casper event. The problem is if I call spooky with url A, then straight away call spooky with url B, and then url C, whenever the first url is finished rendering to a file, I get THREE 'capture.saved' events.. all calling back with the same image of the first url to have finished rendering, even though only ONE url has been captured. Then later on.. I will get TWO more 'capture.saved' events for the remaining urls in whatever order the requests finish. These last events call back with the correct image for the url.

I've put together a simple gist which can be run that demonstrates the issue: https://gist.github.com/cjroebuck/5580502

Hopefully this is something stupid I am doing and there's a simple workaround as its been driving me nuts.. thanks

[lawnsea]

Huh. That's odd. I'll look into it. Thanks for the report!

[tomchentw]

The reason is wrong prototype chain used in Spooky. This bug costs me few hours to solve. I'll fill a PR.

Updated:
#60