Websockets.unitypackage example doesn't work anymore?

I tried this package like 3-4 months ago and it worked fine.
http://files.unity3d.com/jonas/WebSockets.unitypackage

We even had a part of game with websocket working with WebGL for a while. (it was in the Unity5 beta)

Today I checked for a WebGL export, and it just hang in Firefox. I got no error or crash, and the CPU and the memory are changing.

And I found out it seem related to the websocket. I can reproduce the problem only with the websocket example package.

Anyone know why?

I use 5.1.2f1, Firefox 39.0 on Windows 7

 

which problems do you experience exactly?
i'm using the .jslib from this package without
any real troubles (rewrote some parts on my own thou)

 

Firefox just hang, no error or crash

 

any code that's run? have you tried some print calls to your js-console to debug where it's happening? which library functions do you call?

 

I didn't try to debug directly the jslib, but when I do, I'll update the post.

I only call that:

Code (CSharp):

1.    
2. public IEnumerator Start()
3.     {
4.         Application.logMessageReceived += OnLog;
5.  
6.         WebSocket w = new WebSocket(new Uri("ws://echo.websocket.org"));
7.         Debug.Log("Trying connect...");
8.         yield return StartCoroutine(w.Connect());
9.         Debug.Log("Connected");
10.         w.SendString("Hi there");
11.         int i=0;
12.         while (true)
13.         {
14.             string reply = w.RecvString();
15.             if (reply != null)
16.             {
17.                 Debug.Log ("Received: "+reply);
18.                 w.SendString("Hi there"+i++);
19.             }
20.             if (w.Error != null)
21.             {
22.                 Debug.LogError ("Error: "+w.Error);
23.                 break;
24.             }
25.             yield return 0;
26.  
27.         }
28.         w.Close();
29.     }
30.  

 

why do you try to do this endless IEnumerator in start?

simply put your message-handling in the update() and get rid of this while(true) construct...

my guess is that since the coroutine you fork off in start never finishes unity never gets over the initialization phase, so you've basically halted in an endless loop before you even get to the main event loop

 

You should read about coroutine, it work well. And this code come from the unitypackage from Jonas Echterhoff

 

This appears to have broken in unity 5.1.2. Surprised more people haven't run into it.

I don't use the unitypackage in question, however I have the same issue. Essentially, Marshal.FreeHGlobal is crashing. Unfortunately I don't know of a good fix, other than to not release the memory in question. Hopefully this is fixed with a patch soon.

 

It looks like this is closed by design... http://issuetracker.unity3d.com/issues/webgl-socket-plugin-no-longer-working

I'm not sure why though, and am pretty annoyed that a breaking change like this was introduced without notice in what appeared to be a small update (between 5.1.1 to 5.1.2 should only really be for bugfixes imo...)

 

Thanks for the info, that's really bad for us.

 

FWIW you should be able to replace it with passing strings directly, it's just annoying that they broke the current way it works.

 

My bad, I didn't know it was on the asset store..

I updated and everything work great.
Thanks!