Unity crash when loading scene

Hey guys, I am running OSX 10.10.2 on Macbook Pro, Unity 4.6.2f1, and I am using the Oculus Rift SDK 0.4.4. I get this error when I load one of my scenes in the editor. Unity crashes and these seem to be the most relevant parts of the log file:

Spoiler

WARNING: Shader Unsupported: 'Example/Rim_dust' - Pass 'FORWARD' shader state not supported
GPUProgram: loaded 1:159216d3698f42bdeee01dc73681d624 kwords 0000000000085028 from cache in 0.71 ms

This is followed by many more of the "GPUProgram: loaded" lines and then:

Spoiler

Unity(4229,0xa03e41d4) malloc: *** mach_vm_map(size=5640192) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory!
Trying to allocate: 5592432B with 32 alignment. MemoryLabel: Texture
Allocation happend at: Line:411 in /Users/builduser/buildslave/unity/build/Runtime/Graphics/Texture2D.cpp
Memory overview

And then:

Spoiler

[ ALLOC_PROFILER ] used: 211863B | peak: 0B | reserved: 8388608B
Could not allocate memory: System out of memory!
Trying to allocate: 5592432B with 32 alignment. MemoryLabel: Texture
Allocation happend at: Line:411 in /Users/builduser/buildslave/unity/build/Runtime/Graphics/Texture2D.cpp
Memory overview

I should also note that when this happens a white window appears within the unity editor covering the "Game" view. It does not go away unless the game view is moved or Unity restarts. Unity also does not always crash the first time the scene loads but will always crash the second time.

Thanks a lot for reading. Please let me know if there is any additional information I should post.

 

Clearly it's running out of memory Are you able to use the profiler at all and see if there's a giant leak?

I have zero knowledge of anything, however, and your errors are mostly gibberish to me.

 

It is odd to think that my system is running out of memory since this game was working perfectly fine before. I will profile it and see if I can dig up any clues.

 

So my system is not running out of memory. In fact, Unity barely exceeds 2.0 GB of memory. The profiler itself doesn't lend much useful information since it stops updating with information as soon as the game crashes and nothing super relevant shows up before then.