Unity crashing on asset import

This has happened to me since around 3.4 on and off. It’s still happening in Unity 4 :expressionless:

I import unitypackage files either from my hard drive or downloaded from the asset store and randomly Unity crashes.

Anyone else having this issue, a search didn’t bring anything up.

I’ve had this happen when I was low on RAM.

My system has 8gb of ram, less than half is being used normally.

Happens to me, Unity 4.0, every time when importing NGUI, either local or “from store” (also uses local package, I think).

Can you please file a bug report and include the package that makes it crash?

Best regards
Steen

1 Like

Just a couple of notes from my experience today…

  • The decompression and import utility doesn’t check disk space as it’s working, so if a drive runs low on space, it doesn’t error out.
  • On my older development computer, upon importing the mecanim example complete scenes package, it pegged the CPU at 100% for several minutes. The system was usable, but I would only see the Unity progress bar a few times during the entire process. I don’t know what it’s doing as it’s importing fbx files, but it’s very busy doing something. After what seemed like a very long time, it did finish and I was able to try all the examples without any problems. Performance was not an issue.
  • There was no bug report to file, because in my case, it never crashed. It would either hang (insufficient disk space) or just seem to hang.

Anyway…I have to two recommendations:

  • Test importing the mecanim examples scene on some computers with older processors.
  • Test importing the same package onto a drive with insufficient disk space.

Have the system requirements for Unity changed? That would be something that is good to know.

Cheers

So I’ve been having this problem because I don’t have any choice but to upgrade to OS Lion since I need to be able use Xcode to build to iOS. I have a mid 2007 MacBook that I just upgraded to Lion. I’ve had this problem before, making me revert back to snow leopard where the asset importer won’t crash and lock up the whole system. I’m not sure if its a CPU issue since importing stuff sends the CPU sky high for the whole time. When i restart the mac thats when unity tells me the asset importer failed to import something. Are the requirements for Unity different when it comes to Lion OS compared to Snow Leopard OS?

Buying a new MacBook is not an option of course(even though there are people here with newer models having the same problem so what difference does it make…)

i doubt forum users will be able to help you with that (esp. since you dont provide any details).
Please, bug report with repro project and as much info as possible.

Hey Alexey. I don’t have a repro project, since the crashing also happens when I import into an empty scene, I don’t exactly how to repro.

but you DO import something into an empty scene? :wink:
So attach this to bug report

Same things is happening to me, really annoying.

guys, seriously, stop whining and bug report. If you have “something failed to import” check FailedAssetImports.txt in Library folder.
Grab empty project and drop here (and change import settings if needed).
I mean - we CANT fix something we dont see ourselves

I cannot submit a bug report because whenever I do it says, “Failed to Report”, or something of the sort.

After searching through the forums for an answer, I found this thread (yes, I know it’s an old thread but figured it would be better to add to an old one than start a new one with the same question) and I’ll add my situation as well in hopes of some advice.

Not only does Unity crash when importing my downloaded asset from the asset store (Medieval Environments is the asset, btw), but my entire system shuts off halfway through the importing phase! This happens when importing the asset as a whole into an empty scene or when opening a project that has that asset inside of it. I’ve managed a workaround and just import it in bits and pieces but once it’s in imported in it’s entirety, when attempting to reopen the project, it causes my entire system to shut down.

It gives me no option to send a bug report and I am at my wit’s end on how to address the issue. I’m running windows 7 with 6 gigs of DDR3 SDRAM and an AMD 3.1 gig Quad-Core CPU. I am keeping a RAM and CPU monitoring program up while attempting imports and it’s saying i’m using about 1/3rd of my RAM and ranges from 35% to 100% of my CPU, fluctuating constantly.

I’m brand spanking new to Unity (just got a few assets and the program for my birthday) and it’s becoming a huge turn off for me so far. Any advice would be greatly appreciated.

I am having trouble with importing assets as well. Ever since I downloaded Unity again after a year in June, I cannot import ANYTHING except for terrain without it crashing. I sent in 3 error reports, but I have heard of nothing since. I believe whatever the specs in computer are, they are not compatible with that version of Unity. Because last year or sometime before March of this year, I had Unity downloaded and it worked fine. Since July, has there been any newer versions of Unity? Can I also download previous versions as well?

I’m having the same issue, only I have isolated it down to my anti-virus software Total Defense. The issue is that I’ve given Unity all the permissions I can, but it still crashes, and THEN it crashes every time on start up, until I put Total Defense into “snooze” mode.

I would LOVE to be able to send error reports, but when I try it just sits there at about halfway done compressing report and never finishes. I have Unity 4.3 and this is the error:

**

[quote]**
GetPersistenManager ().WriteFileInternal (metaDataPath, metaDataFileIndex, writeData.begin(), writeData.size(), NULL, BuildTargetSelection::NoTarget(), 0)
**[/quote]
**

My FailedAssetImports.txt is empty as well.

{{{I also sometimes get:

**

[quote]**
Opening file Library/FaileAssetImports.txt failed: The process cannot access the file because it is being used by another process.
**[/quote]
**

Even when Unity is shut completely down. Though this may be a conflict with Notepad++ since it can hold the last txt session open when it itself is closed. (Tested and that problem went away when I turned Notepad++ remember last session option off.)}}}

Hi,

I have the same crash when importing package. I have nothing into FailedAssetImports.txt.
I always import upgraded package in a new scene so I can erase previous plugin (in unity Project tab) and import the package by executing the unitypackage file.
In the editor.log, it succeed to import all files, re-build the whole project, unloading some unused assets.
Then check for an update then:

I attached the whole log file if you want.

I hope it will help you.

-Tinken

more info:
Working on Mac os 10.8.5
3.1 Ghz intel core i7
Ram: 16Gb DDR3
space on my drive 400Gb free on 1Tb

1586164–94913–$Editor.log.zip (18.7 KB)

I think I found the issue:
I have a tab always open of this plugin. When I delete the plugin it doesn’t close the tab.
I import the update and maybe there is a display update at the end of all compilation and the code has changed maybe the guid and it crash.
:!: It needs to be checked again. :!:

-Tinken

@tinken that looks scary. please, try to repro with empty (or almost empty) project - the point is to have minimal repro. As i understand you just frop the package to unity, right? so - project + package, zip it and bug report with repro steps. Drop case number here i’ll poke appropriate people to look at it.
@RazielSilver yes, your errors seems to indicate that something is holding the files in exclusive mode. AntiVirus software is well known for that funky behaviour

I have the same problem with blender imports. When I try to import a blender file, unity opens blender and in my taskmanager and I see that blender use every second more “main memory” (RAM). When I stop the process I can use Unity, during the import Unity freeze. So has someone found a solution yet? Or could the unity technologies help me please?