Segmentation Fault

[jfhbrook]

Hey hey,

I tried running the tests for spider, and I consistently get behavior like the following:

josh@pidgey:~/spider$ node tests/test_nytimes.js 
Segmentation fault

Frustratingly, that's all the information I get.

Any ideas?

[jfhbrook]

Update: I found the offending line:

Script.runInContext(jquery, ctx, filename);

Instead of failing gracefully (or running successfully), this causes a segfault for me.

I'd try and fix it, but I don't really know exactly what process.binding('evals').Script does so I don't know where to start.

[jaehess]

I am seeing this also, but I am getting Segmentation Fault 11, is it possibly related to the same error as Zombie?

assaf/zombie#183

[vecter]

I think in node.js 0.6+, it should be process.binding('evals').NodeScript, not .Script.

Could it have to do with the fact that this hasn't been updated for Node 0.6?

[vecter]

I also had to update jquery from 1.4.2 to 1.7 (it tried to access "navigator" and "location", which are now bound to window).

now i get a new error message:

Kevins-MacBook-Air:tests kevin$ node nyt.js
The "sys" module is now called "util". It should have a similar interface.

/Users/kevin/git/spider/main.js:59
Script.runInContext(jquery, ctx, filename);
^
ReferenceError: setTimeout is not defined
at Function.bindReady (/Users/kevin/git/spider/jquery.js:455:11)
at [object Object].ready (/Users/kevin/git/spider/jquery.js:276:10)
at [object Object].init (/Users/kevin/git/spider/jquery.js:198:22)
at /Users/kevin/git/spider/jquery.js:27:10
at /Users/kevin/git/spider/jquery.js:1518:2
at /Users/kevin/git/spider/jquery.js:1615:2
at /Users/kevin/git/spider/jquery.js:9266:2
at /Users/kevin/git/spider/main.js:59:12
at Spider._handler (/Users/kevin/git/spider/main.js:201:5)
at Request._callback (/Users/kevin/git/spider/main.js:175:12)

I moved the Script.runInContext outside of the try/catch to show the stacktrace. my whole jqueryify function looks like this:

47 jqueryify = function(window) {
48 var filename = jqueryFilename;
49 var document = window.document;
50 if (window) {
51 var ctx = window.scriptContext;
52 if (!ctx) {
53 window.__scriptContext = ctx = new Context();
54 ctx.__proto = window;
55 ctx.window = window; // <------ NEW
56 }
57 var tracelimitbak = Error.stackTraceLimit;
58 Error.stackTraceLimit = 100;
59 Script.runInContext(jquery, ctx, filename);
60 /* try {
61 Script.runInContext(jquery, ctx, filename);
62 }
63 catch(e) {
64 document.trigger(
65 'error', 'Running ' + filename + ' failed.',
66 {error: e, filename: filename}
67 );
68 } */
69 Error.stackTraceLimit = tracelimitbak;
70 }
71 };

If I change the call of setTimeout to window.setTimeout (that is, actually modifying jquery.js), i jus get a Segmentation fault: 11.

[mikeal]

so, the only reason we are doing this by hand is that I didn't have a way to get jsdom to cache the text of the jquery script, it insists on loading it from disc for every eval.

if jsdom could get have a better way to eval or keep files loaded from cache we could remove this from spider. jsdom has far more users and will do a better job long term of keeping this up to date with recent releases of node.js.

[jfhbrook]

Could it have to do with the fact that this hasn't been updated for Node 0.6?

This issue was filed well before people were even using 0.5.x

[vecter]

I was able to fix the jqueryify function by replacing process.bindings('eval') with require('vm') (new in node 0.6). Now it gives Segmentation Fault: 11 at

r.fn.call(r, window, window.$);

i'm on mac os 10.7 running node.sj 0.6.0. Anyone else getting this, or just me?

[dklanac]

Yes, I am getting Segmentation fault 11 on 10.7.2 running node 0.4.10

[sesam]

If is this still an issue for people:

• which versions (node, jquery, operating system, etc) are working / not working?
• for those where it's not working, what are you using / doing to get your tasks done?