I’m having a serious crash issue with Unity, and I can’t get to the bottom of it. This problem has persisted and is growing in frequency over the last 2-3 weeks, and currently I can produce nothing from this project.
There are three possible variables:
Unity 3.0x
EZGui/SM2 from A&BSoft
My project
The behaviour is like this:
When working with prefabs, usually instantiating them, tho’ I’ve had this issue with editing a prefab in the inspector (usually, but can’t say always, the instantiated ones…), and once even picking “create prefab” from the drop down menu. Moreover, when I say “editing” this can easily be just tabbing from one field to another.
This is not happening on every prefab. It seems to be happening only on selected prefabs… eg: This one is a crasher and this is not. These prefabs seems to only be prefabs with EZGui scripts attached, but I have not yet tested every one of the many prefab in my project to be 100% sure others won’t fail. I have compared the crashers side by side (as ones in the project window are usually stable as long as they are not instantiated, whereas an instantiated prefab could be a land-mine by manipulating them in any way…) with the non-crashers and they seem identical. No other EZGui user reports this behaviour.
The console always seems to say:
… but I’m not savvy enough to see what exactly that’s responsible for this unhandled NULL.
Steps I’ve taken:(other than report these to the higher authorities…)
I have done a reimport all (a few times), which has no apparent effect.
I have tried to rebuild the offending prefabs.
I have saved the scene as a new scene.
I have created some new empty projects and tried to replicate the issue and it won’t recreate. That being said…
I have reopened previously stable projects from one or two weeks and one or two months back, and they exhibit this behaviour. This worries me, because they were stable under previous version of Unity and previous versions of EZGui… and as the only thing changing is Unity from 2.6 to 3.0…
I’ll put up more information as I get it, but right now I’m skuppered. I can only think I’ll have to try and rebuild this project from it’s elements, but if the behaviour is expressed in a project 2 months old that was stable… it makes me worried that I’ll be rebuilding something that still won’t work.
I have reported everything except passing on the project as it’s 555mb and have not yet made arrangements with support the best way to get this over to you. Could be disk in post? Or long ftp transfer? I find that often the unity bug reporter would fail on large files. I have just now started making space for the upload on one of my sites.
I’m not convinced it’s 3.0, per se, but I just have too many variables to start narrowing it down at all.
Removing that space also seems to have removed the prefab crash issue.
What is very odd is that, in an effort to prove that the space was the actual issue, I reintroduced the space in the Unity directory name, and I could not reproduce the crashes. They have literally vanished after three weeks of heck. A have a list of damaged prefabs that were consistently crashing the project and now all of them appear clean.
Between now and then I have opened and closed Unity a number of times using a 3.0f5 and 2.6, and I have opened several copies of the project in both packages and I’ve up[graded several old projects to 3.0f5, however, the one key change was removing the space from all copies of Unity (including 2.6 and 1.7) and since then I have not been able to recreate this crash in any manner.
With hope, this was the issue and it is now solved.
/me goes off to find a pint of ale.
*The alternative answer is that Joachim Ante (Who I am always going to remember as Joe the iPhone cleaner…) went back to his office and performed an arcane ritual and exorcised the demons plaguing my project! Thanks, Joe!
Not sure how that change in the directory name made the problem apparently vanish, but it’s back now after a few days of work and no apparent change in the project except “more work” …
There are several bug reports on this, but it seems the main one is 375322
I’ve sent the test project as well (sending - it’s churning away…).
yOrsh: I’ve started rebuilding my project from the elements, as no one was able to find the answer to this, and you are the only other person to have reported this. We should coordinate and try to figure out what is similar between our projects…
It happened to me twice yesterday. My first project become corrupt because of this bug so I started another one. At 3 AM the same thing happened so I just ended cursing and going to bed.
Do you have gtalk? (my email is jorgelorenzon at gmail.com)
Mmmm… No. Don’t have g-talk. But we should look at things like… systems, video cards, saving methods. Sounds like your project was relatively new. Mine was huge and old and upgraded from Unity iPhone 1.5 (or earlier) all the way through 2.6 and 3.0 betas to final.
It needed a cleaning, but I hate to have a corruption be the reason.
I’ll point your bug report to my bug report(s) and gather some information here but I’m “painting” a model, and won’t be free for a while.
EZ GUI:
I use prefabs that have in them: GUI Camera, buttons, sprites, sprite manager (I have managed sprites), ui manager. Then by code I instance the prefab to get my gui up.
When Unity crashed it had been opened by MonoDevelop.
What is the exact cause of your crash? What are you doing to what object that actually does it? Can do you know how to access your console for get the Unity Editor logs? (BTW: What platform? Mac/Win?) Do you know what the actual exception is?
There is one know issue that has been solved, but it only manifests in Managed sprites, whereas my problem was potentially any EZGUI prefab, so we may have unrelated issues.
Check with Brady, see if you have this issue and if so, get his fix, otherwise, let’s keep talking.
It is possible I have a fix for this. If it is what I’m thinking of, it only happens in very specific circumstances. Contact me and I’ll send you the internal version of the next release which includes a fix.
Personally: Just to be clear. All evidence points towards a corrupted project or perhaps a problem with my video card. Too many variables, and I’m rebuilding the project. Perhaps we will never know. For all my other projects EZGui has been completely stable.