|
Is there any possible way to stop the editor from crashing anytime it receives an exception? It would be useful to just have the "game" crash - instead of having everything go down in flames. It makes debugging very difficult, since these errors are only thrown in unity and not in other test environments. Any ideas would be very helpful.
(comments are locked)
|
|
Do you get this message in the Console after starting Unity? If so, do what it suggests! No, i guess he's "producing" an exception that isn't handled in his game and that terminates the Unity editor when you test in the editor. Usually all exceptions related to the Unity API are caught by Unity itself and displaying an error in the console. I guess he's using something from the .NET / Mono library that is quite sensitive against misuse like: Threads, FileIO, Networking / Sockets, other OS native code related things. There is a small chance of a bug in Unity, but most the time it's a fault by the user ;) Btw, this question is 2 years old and the OP wasn't online since then ... ^^
Jun 19 '12 at 12:03 PM
Bunny83
Umh, must have clicked it in the "Related Questions" suggestions and then answered by instinct, sorry. It's confusing (but obviously intentional), that these usually refer to ancient questions.
Jun 19 '12 at 12:13 PM
Wolfram
:) Well, unanswered, buried questions also deserve an answer ;) Otherwise it would make more sense to delete the whole question...
Jun 19 '12 at 06:10 PM
Bunny83
(comments are locked)
|
can you be a bit more specific on what kind of exceptions you are getting? Perhaps even throw in a few lines of stacktrace?
if you're in doubt how to find a stacktrace, look at this answer: http://answers.unity3d.com/questions/2252/how-can-i-find-editor-log-file. If Unity crashes, the Editor.log ends with a Stacktrace followed by some lines starting with "at". The stacktrace can help identify a problem in some cases.
You can also display a stack trace from your own code by using System.Environment.StackTrace (doesn't help on a crash, but might help in the process of narrowing down where the crash is occurring.)
@Nicolaj I noticed your link is now dead, that is the problem with linking to older questions/answer, they don't stay around for as long as the newer question