Unable to use web client on chrome 40/41

BYOND Forums

Announcements · BYOND Help · Bug Reports · Feature Requests · Beta Testers · Beta Bugs · Developer Help · Design Philosophy · Demos & Libraries · Tutorials & Snippets · Art & Sound · Classified Ads · Game Updates · Contests & Events · Linux Talk · On Topic · Off Topic

ID:1804223

Mar 7 2015, 5:30 pm (Edited on Jan 21 2021, 9:42 am)

Codingale

Resolved

BYOND Version:	507
Operating System:	Windows 7 Ultimate 64-bit
Web Browser:	41.0.2272.76 (Official Build) m (previously: Chrome 40.0.2214.115 )
Applies to:	Webclient

Status:

Resolved (web)

This issue has been resolved.

Descriptive Problem Summary:
Unable to launch game

Numbered Steps to Reproduce Problem:
Hangs at (Dead Link)
After almost all resources are downloaded etc.

Code Snippet (if applicable) to Reproduce Problem:

webclient.dart.js:13264 Setting DOM load callback
webclient.dart.js:13264 Creating byond function and module
webclient.dart.js:13264 Adding bind and curry functions
webclient.dart.js:13264 Creating skin module
webclient.dart.js:13264 Creating prompt function and module
webclient.dart.js:13264 Creating lightbox module
webclient.dart.js:13264 Creating event module
webclient.dart.js:13264 Creating byond.fn methods
webclient.dart.js:13264 Creating byond.winsetfn methods
webclient.dart.js:13264 Checking for DOM load
webclient.dart.js:13264 Adding listener for DOM load event
webclient.dart.js:13264 DOM load event
webclient.dart.js:13264 DOM load detected
webclient.dart.js:13264 DOM loaded
webclient.dart.js:13264 Creating client
webclient.dart.js:13264 Setting host and port
webclient.dart.js:13264 Doing reset
webclient.dart.js:13264 Creating byond function and module
webclient.dart.js:13264 Adding bind and curry functions
webclient.dart.js:13264 Creating skin module
webclient.dart.js:13264 Creating prompt function and module
webclient.dart.js:13264 Creating lightbox module
webclient.dart.js:13264 Creating event module
webclient.dart.js:13264 Creating byond.fn methods
webclient.dart.js:13264 Creating byond.winsetfn methods
webclient.dart.js:13264 Checking for DOM load
webclient.dart.js:13264 DOM has already loaded
webclient.dart.js:13264 DOM load detected
webclient.dart.js:13264 DOM loaded
webclient.dart.js:13264 Begin render loop
webclient.dart.js:13264 Getting user ID
webclient.dart.js:13264 Opening Websocket
webclient.dart.js:13264 Client creation complete
webclient.dart.js:13264 Removing listener for DOM load event
webclient.dart.js:13264 Socket: open
webclient.dart.js:13264 Version: 507, 498
webclient.dart.js:13264 Begin loader setup
webclient.dart.js:13264 StageXL render engine : Canvas2D
webclient.dart.js:13264 Adding items to loader
webclient.dart.js:13264 Loader creation finished
webclient.dart.js:13264 Quit: code 9
webclient.dart.js:13264 Socket: close
webclient.dart.js:13264 All resources loaded
webclient.dart.js:13264 Beginning skin load
webclient.dart.js:13264 Loading byondprompt alert
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondprompt any
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass bar
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass browser
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass button
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass child
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondprompt color
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass dpad
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondprompt file
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass grid
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass hotbar
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass info
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass input
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass label
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass map
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondprompt message
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass output
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass pane
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass pop
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass status
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass tab
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondprompt text
webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Loading byondclass verbmenu
3webclient.dart.js:13264 Loading styles
webclient.dart.js:13264 Generating default styles
webclient.dart.js:13264 Filling skin HTML
webclient.dart.js:13264 Creating skin controls
webclient.dart.js:13264 Activating map
webclient.dart.js:13264 StageXL render engine : WebGL
webclient.dart.js:13264 Ready to begin play

Expected Results:
Something more?

Actual Results:
Black screen.
Does the problem occur:
Every time? Or how often? Every time.
In other games? Unknown
In other user accounts? Unknown
On other computers? Unknown (Tested on latest IE and Chrome, Chrome Canary, Firefox)

When does the problem NOT occur?
Unknown.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)

N/A

Workarounds:

N/A

Mar 7 2015, 6:26 pm
Super Saiyan X	Do you have hardware acceleration turned on in Chrome? I recall having issues loading the webclient when I had it turned off.

Mar 7 2015, 6:52 pm
Codingale	Tried having it disabled instead and nothing happened. Enabled it and it didn't work. Also tested it on more browsers. Are you able to connect. Does this work for SS13 yet? Only a few servers?

Mar 7 2015, 9:56 pm
Super Saiyan X	It seems to work fine for me, I'm running Chrome 42.

Mar 8 2015, 12:03 am
Codingale	... Quit: code 9 webclient.dart.js:13264 Socket: close webclient.dart.js:13264 What about that error, got it at the end when updating to chrome 41. Now at version: 41.0.2272.76 (Official Build) m Unable to play any games. I don't rightly see how you're on Google chrome 42 and not on Canary; or are you?

Mar 8 2015, 1:36 am
Codingale	Hum found out if I delete the overlay (the black screen and stuff) it says the server closed connection or something. Any suggestions?

Mar 8 2015, 7:50 am

In response to Codingale

Super Saiyan X

Codingale wrote:

...
Quit: code 9 webclient.dart.js:13264
Socket: close webclient.dart.js:13264
What about that error, got it at the end when updating to chrome 41. Now at version:
41.0.2272.76 (Official Build) m
Unable to play any games. I don't rightly see how you're on Google chrome 42 and not on Canary; or are you?

I'm running the dev build of Chrome.

Are you able to connect to the server normally using Dream Seeker on the same system?

Mar 8 2015, 12:32 pm
Lummox JR	Quit code 9 means you had an authentication problem. Are you trying to connect to your actual external IP, or is there some kind of unusual router-in-router setup you're using? Connecting to localhost ought to always work as well.

Mar 8 2015, 7:24 pm

Lummox JR

Codingale wrote:

I'm connecting to a server I can connect to via Dream Seeker on the desktop.

That doesn't answer my question, though. We've run into some issues with some weird router-in-router setups, and so a complex local network might explain the issue.

The IP address of the server is relevant to this issue, and if it's not the same address that the server itself thinks it has, there's the problem.

Mar 9 2015, 6:37 am

Lummox JR

I suspect the name resolution is the main issue. That's something I can look into. This ultimately should be going by the address that the webclient used to connect, but maybe there's something fishy involved.

However if you're not the one running the server--which is what I thought you were doing--I have no idea what version they're using. It's possible they're on an older webclient build that didn't handle this correctly, and if that's the case I really don't want to waste time chasing a bug that's long been fixed. I'd need to talk to the people running the server to find out more.

Mar 9 2015, 11:54 am
A.T.H.K	The domain does have an A record, but it doesn't even work going straight to it.. http://87.117.225.100:22000 http://87.117.225.100:22000/play/ Do not work where as my chatters instance does http://162.251.70.58:295/play/ I would say they have either listed the wrong domain, haven't updated the IP or don't actually have the web client enabled at all...

Mar 9 2015, 12:11 pm
Lummox JR	My guess is they're using an outdated version.

Mar 9 2015, 8:56 pm
Lummox JR	I found the culprit behind this, which matches another issue. I'll merge the threads at some point.

Mar 9 2015, 8:56 pm
Lummox JR	Lummox JR resolved issue

Mar 10 2015, 12:10 am
A.T.H.K	503? We're up to 507. 503 wouldn't have the web client.

Mar 10 2015, 6:34 am
Lummox JR	Codingale, ATHK is right; 503 does not support the webclient. The server has to be running one of the 507 builds to run the webclient at all. 503.1224 may be the version you're using for BYOND yourself (if so you should stop using it, and upgrade to at least 506), but that has nothing to do with the server's version or with webclient support. Anyway the issue was web-side.