Search Unity

[url]WWW.LoadUnityWeb[/url] crash

Discussion in 'Editor & General Support' started by Deleted User, Oct 17, 2007.

  1. Deleted User

    Deleted User

    Guest

    I consistently get a browser crash (on Mac) with WWW.LoadUnityWeb. I already mentioned this in another thread and submitted a bug report over the weekend, but I haven't heard confirmation or anyone else mention this problem.

    So if anyone wants to try crashing their browser, you can try loading:

    http://www.fugugames.com/fugudemo.html

    and clicking on any of the icons to load a game via WWW.LoadUnityWeb.

    Here's the portion of a firefox crash stacktrace that seems relevant:

    Code (csharp):
    1.  
    2. Exception:  EXC_BAD_ACCESS (0x0001)
    3. Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x1915eff0
    4.  
    5. Thread 0 Crashed:
    6. 0   <<00000000>>    0xffff0af0 __memcpy + 848 (cpu_capabilities.h:228)
    7. 1   libstdc++.6.dylib               0x90b2e31d std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_copy(char*, char const*, unsigned long) + 43
    8. 2   libstdc++.6.dylib               0x90b2f819 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_mutate(unsigned long, unsigned long, unsigned long) + 181
    9. 3   libstdc++.6.dylib               0x90b300ea std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_leak_hard() + 70
    10. 4   libstdc++.6.dylib               0x90b301c4 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::begin() + 18
    11. 5   dk.otee.UnityWebPlayerCore      0x11367f5c 0x11364000 + 16220
    12. 6   dk.otee.UnityWebPlayerCore      0x1139b24a 0x11364000 + 225866
    13. 7   dk.otee.UnityWebPlayerCore      0x11399391 0x11364000 + 218001
    14. 8   dk.otee.UnityWebPlayerCore      0x114a2101 UnityBundleLoop + 200069
    15. 9   dk.otee.UnityWebPlayerCore      0x11394173 0x11364000 + 196979
    16. 10  dk.otee.UnityWebPlayerCore      0x11394a7f 0x11364000 + 199295
    17. 11  dk.otee.UnityWebPlayerCore      0x1147168c UnityBundleLoop + 784
    18. 12  com.unity.UnityWebPlayer        0x01eb3bee UnityWebPlayerPluginInstance::HandleEvent(void*) + 1792
    19. 13  com.unity.UnityWebPlayer        0x01eb3dbb NPP_HandleEvent + 147
    20. 14  com.unity.UnityWebPlayer        0x01eb4e46 Private_HandleEvent(_NPP*, void*) + 24
    21. 15  org.mozilla.firefox             0x007046c1 ns4xPluginInstance::~ns4xPluginInstance [in-charge deleting]() + 317
    22. 16  org.mozilla.firefox             0x0061ec55 nsPluginInstanceOwner::Paint(nsRect const, unsigned) + 155
    23. 17  org.mozilla.firefox
    24.  
     
  2. David-Helgason

    David-Helgason

    Moderator

    Joined:
    Mar 29, 2005
    Posts:
    1,104
    It doesn't crash at all here (newest MacBook Pro 15", Safari 3.0.3), but there is some error in your data-file which prevents Unity from loading it.

    It's great that you submitted a bug. The bug queue is still working, but a server problem is preventing them from actually being put into our bugtracker. We're working on that, so we'll be seeing you bug soon.

    d
     
  3. Deleted User

    Deleted User

    Guest

    David, what data error do you see? Is it in loading the menu scene, or after selecting one of the games? Maybe it's the same problem, although I can load and run every game individually, bypassing the menu, so I think it's gotta be something to do with WWW.LoadUnityWeb.

    I forgot to include the firefox and safari stacktraces in the original bug report (was waiting for the auto-response, so I could reply with that info, especially if you guys couldn't reproduce it)

    FYI, http://www.fugugames.com/fugudemo.html is just the Unity 2.0 version of http://www.fugugames.com/unitygames.html, i.e. the web page uses the new clsid to specify the Unity web plugin, and all the web players are rebuilt with Unity 2.0 and saved with the new .unity3d suffix instead of .unityweb.

    The original http://www.fugugames.com/unitygames.html still runs fine, as it it's still using Unity 1.x, both plugin and players. Another test I ran was just changing that web page to use the 2.0 plugin but still loading the 1.x players. That also loads the menu player fine and then crashes when loading one of the games (but it's good to see that the Unity 2.0 web plugin otherwise seems to run 1.x-built players fine!)

    Next step: I'll see if it crashes on Windows.
     
  4. Gorge

    Gorge

    Joined:
    Oct 17, 2007
    Posts:
    3
    It crashed my browser. I clicked on "Bowl" then my browser crashed. Using Safari 2.04 on a mac mini

    :eek:
     
  5. Joachim_Ante

    Joachim_Ante

    Unity Technologies

    Joined:
    Mar 16, 2005
    Posts:
    5,203
    You can't load 1.x unityweb files using a 2.x player. If you go with 2.x do not stream in 1.x unityweb files. So either you go with a 1.x player all the way or you go with a 2.x player all the way, but you can't mix and match. You also can't mix and match the new html with the older 1.x default html.
     
  6. Deleted User

    Deleted User

    Guest

    OK, good to know (would be great to have an upgrade guide for existing deployed web pages - took some trial and error for me to discover the .unity3d was the new automatically-added suffix and that the plugin had a new clsid)

    In any case, fugudemo.html is the default HTML for Unity 2.0 and is passing .unity3d files to WWW.LoadUnityWeb. I just verified that loading it and clicking Bowl also crashes on my XP system (Bootcamp) on both IE and Firefox. I also uploaded and ran http://www.fugugames.com/FuguBowl.html to verify that I can run the Bowl game by itself (I can tell it's the Unity 2.0 version since the smooth-follow script isn't quite right)

    I realized that I I didn't upload all of the Unity 2.0 versions of my minigames, which exhibits another bug that I reported this weekend - WWW.error apparently doesn't get set for missing files, so if you click on Type in the fugugames menu, for example, the load screen just shows 0% and gets stuck.

    The bug report I submitted for both of these issues just uses the sample code in the WWW.LoadUnityWeb script reference to reproduce them.