PDA

View Full Version : Actionscript Errors


Harv
10-13-2008, 08:43 AM
First time I heard about this was when someone pmed me about it. I said to them that it had never happened before and was probably either a one time thing or that it's to do with their computer.

But then I started getting them too.

An output box pops up and says "Actionscript Error" and then in the output box, shows the error. It is ussually differet each time.

This time I got:

Error #2044: Unhandled securityError:. text=Error #2048: Security sandbox violation: http://www.xgenstudios.com/bob/bob.swf cannot load data from bob01.xgenstudios.com:1028.
at Connection()
at Game()

Edit: This error I got while trying to log in. It was just stuck on the connecting part so I just clicked exit and logged back in again. Another time I recieved this in game in a 3P and one of my opponents disconnected... yet they hadn't.. and were still there... even though I couldn't see him or his troops. Even after he had kille dmy troops as he said, my troops were still there. They weren't invisible since I moved my units on the area where his orb was.

Edit2: Another one

Error #2044: Unhandled securityError:. text=Error #2048: Security sandbox violation: http://core.videoegg.com/eap/6740/html/swf/ModelLoader.swf cannot load data from http://videoegg.adbureau.net/LSERVER/hserver/aamsz=display/rid=11cf7f2202fe7dda22778e7b8b298152/site=facebook/area=fb_xgenstudios_160x600/channel=/expandable=1/isfbml=false/VA=ya/VAI=1/VG=m/VGI=1/ccid=/dim=160x600/pb=xgenstudios/pageid=82894211.
at com.videoegg.adManager.model::ModelLoader/loadModel()
at com.videoegg.adManager.model::ModelLoader()

Harv
10-14-2008, 03:21 PM
Another:

Error #2044: Unhandled securityError:. text=Error #2048: Security sandbox violation: http://core.videoegg.com/eap/6740/html/swf/AdManager.swf cannot load data from http://ds.serving-sys.com/BurstingCachedScripts/Res/Blank_1x1.gif.

Moonkey
10-14-2008, 04:56 PM
That second one looks like it's from one of the ads that show to the side of the game, not BoB itself :)

Thanks though, the first one looks like the server had a hiccup at some point, but I've added some error handling for that situation now.