Closed SamDecrock closed 9 years ago
Could be a bug in decoding payload, I'll check it.
发自我的 iPhone
在 2015年1月14日,上午5:19,Sam notifications@github.com 写道:
I'm getting
EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0) I know it doesn't mean much, so here's a screenshot
— Reply to this email directly or view it on GitHub.
@SamDecrock which version of socketio server you are using?
I'm using socketio 1.2.1 but I just tried it with 1.0.0 and I get the same error.
In my Node.js log I get the following incomming request:
GET /?t=1421345585&EIO=3&transport=polling 200 15.470 ms - 489
It seems to be using polling. Can I force it to use websockets?
Here's a screenshot with more debugging data:
Sorry for the late reply, I just double checked your reply, you should set host to localhost/socket.io instead of localhost. But anyway, the crash should be fixed.
I get this crash error to ,
this is my codes: (referenced in one roop !) dispatch_async(recommend_report_queue(), ^{ [[DQStatHelper sharedInstance] showAt:post withCurUrl:page]; }); and then I change the thead method to 💯 dispatch_sync(recommend_report_queue(), ^{ [[DQStatHelper sharedInstance] showAt:post withCurUrl:page]; });
and then , crash disappear . maybe fix it by conincident.
i know it's about thread , bug i don't know why.
giving the thread error
please help to solve this problme
I'm getting
I know it doesn't mean much, so here's a screenshot
located in EngineParser.swift
I'm using Xcode 6.1.1