Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
3
Found in
5.0.1p1
Issue ID
698518
Regression
No
Unity reports running out of memory when importing audio file
Import the attached mp3 file. The console reports the following errors and the file fails to import:
Errors during import of AudioClip Assets/Hot jungle day - the relaxing sound of the jungle.mp3:
FSBTool ERROR: Run out of memory.
FSBTool ERROR: Run out of memory.
FSBTool ERROR: Run out of memory.
UnityEditorInternal.InternalEditorUtility:ProjectWindowDrag(HierarchyProperty, Boolean)
UnityEditor.DockArea:OnGUI()
The Editor isn't really crashing though, so we might have the wrong error message there.
Comments (3)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Foldout arrow indent is misaligned in the Inspector when used in Custom Type
- [Android] The Player screen turns black when playing a video under certain conditions
- Search window icons at the bottom are cut off when Search window is resized vertically
- "Try something else?" text label is cut off when searching for a long text in the Search window
- Rendering Debugger window sections do not have a minimum width set when resizing with the slider in the middle of the window
adrianaaaa
Apr 07, 2017 16:53
Same issue with 80MB ogg file. What would be the max size to avoid this?
DADA_universe
Oct 28, 2016 18:35
Same problem. With 32mb ogg file. Frustrating.
YondernautsGames
May 30, 2016 13:30
I'm getting the same problem on Unity 5.3.4 (f1 and p6). Mine is attempting to import a 400Mb wav file. It doesn't seem to matter what I convert it to, the result is always the same error as above.
In my case I'm working on a contract for a company that has provided a number of these kind of size files, so it's quite a large problem for me. Is there a way around this, or is there any way to see where the issue lies on the roadmap (and when it will be dealt with)?