michaelfig
commented
13 years ago I was able to recompile the .swf with more debug logging. I traced my problem to the following scenario:
- In my web socket event callback, I make a few jQuery calls to enable/disable items, then return control.
- My debug logging code shows that a new WebSocketMain is being created (with a different FABridge, and therefore a different localInstanceMap, which is why the null pointer exception happens: the object ID 1 doesn't exist in the second FABridge's map.
- The weird thing is that I can't find out where this new WebSocketMain is being constructed... the AS getStackTrace() says that it's happening at the top level (i.e. no objects above it).
Could it be that Flash is recreating the new WebSocketMain because the old object crashes somehow? If so, how can I find out how the old one crashed?
Thanks, Michael.
gimite
kanaka
Hi,
I can use the WebSocket without any problems on Chrome and IE6 (with the flash fallback), but when I try Firefox 3.6.13, it works for the first few message exchanges, but then dies during a message I send from a button onclick event. Here is the Console log (the Error #1009 shows up each time I click a button).
I've hidden the domain name, replacing everything with private.example.com because I'm not yet sure that the person I'm working on this for would be willing to expose her site to the public yet. Note that I run a policy server on port 843, the main web site is on 5004, and the web socket-enabled web server is on 8100.
[WebSocket] policy file: xmlsocket://private.example.com:843 [WebSocket] connected [WebSocket] request header: GET /_hippie/ws/ab:16011?client_id= HTTP/1.1 Upgrade: WebSocket Connection: Upgrade Host: private.example.com:8100 Origin: http://private.example.com:5004 Cookie: __utma=229512961.963454258.1293130049.1295481209.1295545518.7; __utmz=229512961.1295545518.7.7.utmcsr=XXX:5004|utmccn=(referral)|utmcmd=referral|utmcct=/cgi-bin/Upcoming.cgi; COOKIE-DATA Sec-WebSocket-Key1: 14%27=c80Z99 64 Sec-WebSocket-Key2: * 472 7o8K3 5jeE 9p bo8W * [WebSocket] sent key3: SOMEKEY [WebSocket] response header: HTTP/1.1 101 Web Socket Protocol Handshake Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Origin: http://private.example.com:5004 Sec-WebSocket-Location: ws://private.example.com:8100/_hippie/ws/aucbidder:16011?client_id= [WebSocket] reply digest: SOME-DIGEST POST http://private.example.com:5004/cgi-bin/Upcoming.cgi POST http://private.example.com:5004/cgi-bin/Upcoming.cgi 200 OK 4.61s lai.js (line 128) [WebSocket] received: {"client_id":"0.83394390687782","type":"hippie.pipe.set_client_id"} [WebSocket] sent: {"type":"watch","expanded":[],"shown":["23137","23117","23136","23119","22454","23121","23135","23122","23120","23139","23140","23141","20562","23055"]} [WebSocket] received: {"type":"ready"} [WebSocket] sent: {"type":"watch","expanded":["23119"],"shown":["23137","23117","23136","23119","22454","23121","23135","23122","23120","23139","23140","23141","20562","23055"]} Error #1009: Cannot access a property or method of a null object reference. throw new Error(myErrorMessage[1]); FABridge.js (line 561) Error #1009: Cannot access a property or method of a null object reference. throw new Error(myErrorMessage[1]); FABridge.js (line 561) POST http://private.example.com:5004/cgi-bin/Upcoming.cgi 200 OK 2.01s lai.js (line 128) POST http://private.example.com:5004/cgi-bin/Upcoming.cgi 200 OK 830ms lai.js (line 128) Error #1009: Cannot access a property or method of a null object reference. throw new Error(myErrorMessage[1]); FABridge.js (line 561)The Flash trace log is as follows:
And finally, the Policy Log:
I tried with both the secure and insecure versions, with no luck.
Ordinarily, I would try hunting down the misbehaving code myself, but even after following the instructions in the README.txt and rerunning build.sh, I can't seem to get any of my changes to the code to reflect in the browser. Weird.
I'd be happy to provide more details upon request, Thanks.