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
New Forum User Notice Update to the Unity Editor Software Terms Unite 2023 - Ask the Experts Online

Unity Application Log only says Crash!!!

Discussion in 'Editor & General Support' started by oglepole, Jun 30, 2015.

  1. oglepole

    oglepole

    Joined:
    Jan 25, 2014
    Posts:
    17
    Hey all - I did some digging around, but I could not seem to find many topics that contained my issue.

    Long story short - I have a very, very, large networking project I have been working on for about a year. I want to say for about the past 2-3 months I have noticed that my game constantly crashes. To clarify - the entire screen goes white and I get a "Application has stopped working unexpectedly" window. This happens both in Editor and Standalone. My main issue is that the unity log doesnt give me anything to work with, it literally just says "Crash!!!" for the standalone application. The editor logs never say anything either, the entire editor just crashes and that's it (No error logs, no nothing).

    I tried to reverse engineer my project a bit - removing things that I thought might be causing it, but the time difference for this crash is so random (Anywhere from 1 minute, to 24 hours) - that it makes it VERY hard to go about it this way. So my question is two fold.

    1. Are there any resources out there that I could use to better identify WHAT is causing the crash. I don't get any error messages in the editor, it simply goes into a stopped working unexpectedly state. If there is a better way to find where/what causes this - I can just work around it. This would be my go to solution if anyone can lend a suggestion.

    2. If there is no way to do the above - I am guessing most people will tell me to send it in to QA. Except I have the feeling getting a 15 gig project, along side reproducing the error (which again - ranges from 1 minute, to 24 hours) might have a very...very...long response time. Is there a good way to expedite this process? Suggestions? or do I just need to suck it up and wait?

    I would be grateful for any feedback or suggestions on how to go about finding this error. Obviously I will continue to reverse engineer it, but with such a long down time - it becomes painfully slow to figure out.

    Thank you!
     
    oglepole, Jun 30, 2015
    #1

  2. Graham-Dunnett

    Graham-Dunnett

    Unity Technologies

    Joined:
    Jun 2, 2009
    Posts:
    4,287
    Does it crash on every PC, or just yours? If you use the Profiler does it tell you that memory is slowing increasing? (And perhaps the game is crashing when it's out of memory. Probably not going to happen after 1 minute or 24 hours.) Unfortunately I am not a Windows expert... but there must be some Windows debugging apps that can tell you more. (Back in the day I used wininternals... which MS bought.)

    Getting QA to try and work out what's happening between 1minute and 24 hours is unlikely to get much traction. If you are a Pro customer then I suspect your bug would get higher up the QA list. But as a minimum I think you;d need to be 99.9% sure that the crash happens on every single PC in the world. If you find the work painfully slow, a QA dude seeing a project for the first time, and knowing zero about what the game does and how the project and script is designed is going to be more than painfully slow.
     
    Graham-Dunnett, Jul 1, 2015
    #2

  3. oglepole

    oglepole

    Joined:
    Jan 25, 2014
    Posts:
    17
    Thanks for the input - I have been able to recreate the issue on 3 different CPU's which have a varying degree of CPU/OS/Etc setups. So I am pretty sure its universal. You hit the nail on the head - I really need to find some way to just get a little more information on whats happening after the crash. Ill take a look into your application suggestion. Id like to avoid any QA/Bug Reporting and just try to solve this myself, but I need to find a way to get my foot in the door at least.

    One thing I have noticed is that when I run my server in development mode it has only crashed one or two times. It definitely has an impact on the situation. I don't know what that means... but maybe it gives someone else an idea?

    I guess I could try running the debugger using mono and see if it grabs anything as the application crashes?

    Any other idea's / suggestion would be greatly appreciated!

    Thanks all!
     
    oglepole, Jul 1, 2015
    #3