arcade crashing on safari

0 favourites
  • 3 posts
From the Asset Store
10 Royalty free music tracks for your indie games and projects.
  • I'm not sure if this is a Website issue or a construct 2 issue but some of the games on the arcade seems to crash Safari Version 6.0.2 (7536.26.17). When they do they usually get about half way loaded then the browser is closed with an error log.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Our team is having the same problem. Two of our games posted on FGL for review before the bidding process starts were denied on the grounds that it wasn't running on the newest OSX Mountain Lion with the newest Safari (HTML5 export).

    I'm not currently up to the same os version as that or Safari version, but I had some helpful insight from a developer on site. Here's some of the stack reports:

    0          0x0000000107a7da67 dfgConvertJSValueToBoolean + 119
    1   ???                               0x0000000109861000 0 + 4454748160
    2          0x00000001079aeec0 JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 912
    3          0x00000001079aeb24 JSC::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 52
    4                 0x0000000108517b11 WebCore::JSCallbackData::invokeCallback(JSC::JSValue, JSC::MarkedArgumentBuffer&, bool*) + 593
    5                 0x00000001085d3c73 WebCore::JSRequestAnimationFrameCallback::handleEvent(unsigned long long) + 275
    6                 0x0000000108771feb WebCore::ScriptedAnimationController::serviceScriptedAnimations(unsigned long long) + 187
    7                 0x00000001082d704d WebCore::DisplayRefreshMonitor::notifyClients() + 93
    8          0x0000000107998dfa WTF::dispatchFunctionsFromMainThread() + 266


    We've both tested this in other versions of Safari and Chrome, in Windows and OSX with no luck in reproducing this. Maybe the above info could help, but I honestly think it's Safari being a chump.



    Not sure how to fix it, but in the mean time use this browser instead of Safari. Cheers.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)