Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Hard crash in GameObject::WillHandleMessage

Discussion in 'Editor & General Support' started by tcossairt, Mar 2, 2016.

  1. tcossairt

    tcossairt

    Joined:
    Dec 5, 2013
    Posts:
    129
    So far unable to repro, but our QA has reported a few of these crashes. Any idea what its trying to do or any known causes of crash? (I've seen a few other reports of this in big games when doing a google search, so its not just u)


    eboot.bin!Unity::GameObject::WillHandleMessage(const MessageIdentifier& messageIdentifier) Line 1110 C++
    eboot.bin!Transform::CalculateSupportedMessages() Line 928 C++
    eboot.bin!Unity::GameObject::AwakeFromLoad(enum AwakeFromLoadMode awakeMode) Line 93 + 85 bytes C++
    eboot.bin!PersistentManager::IntegrateObjectAndUnlockIntegrationMutexInternal(SInt32 instanceID) Line 1076 + 70 bytes C++
    eboot.bin!PersistentManager::ReadObject(int instanceID, enum AwakeFromLoadMode awakeFromLoadOverride) Line 1097 + 11 bytes C++
    eboot.bin!Resources_CUSTOM_Load(ICallString path, ScriptingSystemTypeObjectPtr systemTypeInstance) Line 61 + 174 bytes C++
     
  2. tcossairt

    tcossairt

    Joined:
    Dec 5, 2013
    Posts:
    129
    QA has reported this again in our game. This occurs in a creation of a new GameObject (one that we create from a replication in our network system) -- what circumstances would cause unity to crash in this state?

    The message Unity is crashing on is:
    OnTransformChanged
     
  3. Costco

    Costco

    Joined:
    Aug 19, 2014
    Posts:
    7
    Just curious if you ever found a resolution or the root cause? We are seeing something similar using 5.3.
    Thanks!