What Is The "Heap Zone?"

Question

Level 1

138 points

What Is The "Heap Zone?"

Well, here's a new one - for me at least. Getting multiple error messages, "Not enough room in heap zone Result code = -108." What is a "heap zone," and why doesn't it come up in a search of topics?

And of course, how can I make my own personal "heap zone" that much roomier ...?

Weird.

Mac Pro 2X2.8 Quad-Core, Mac OS X (10.5.5), MacBook Pro (2), Ensemble, 2Bus LT

Posted on Dec 8, 2008 5:48 PM

Reply

Answer 1

ghbrett

Level 1

0 points

Dec 8, 2008 6:43 PM in response to Jason Jones3

I am getting similar heap zone error from Graphic Converter 6.3 1386 with MacBook Pro 2 GHz core duo 10.5.5 with 2GB memory working on jpeg file that's only 4.1 MB.

What gives? Oh, only running FireFox, Graphic Converter, and Preview.

Reply

Answer 2

Jason Jones3 Author

Level 1

138 points

Dec 8, 2008 7:28 PM in response to ghbrett

I'm not running ANY additional apps on a Quad-core 2.8 machine, except for Maestro (Apogee Ensemble). Does anybody out there know what this Heap Zone error is about? Pancenter, BJ, Jim? Is this some truly obscure issue that keeps crashing my project!?

J

Reply

Answer 3

DrNik

Level 1

5 points

Dec 9, 2008 12:57 AM in response to Jason Jones3

Hi Jason,

well, the term "heap" is used to describe the memory area where dynamic allocations are being made. Whenever an app requests a new chunk of memory for use, the OS allocates this on the heap. Over time, memory becomes fragmented (like disks) as many allocations and de-allocations are made. Errors such as yours occur when the OS can not find a contiguous block of memory for the requesting app.

Unless your "heap zone" is a totally different beast, then that would be the root cause imho. Either way, you shouldn't be running out of memory this ungracefully. Is the problem consistent or does it go away after a restart of Logic, or even a machine reboot?

Nik.

Reply

Answer 4

Eriksimon

Level 6

15,422 points

Dec 9, 2008 5:42 AM in response to Jason Jones3

Hi Jason,

Is it only in one particular project? It could be that Logic has reached it's 3,5 Gb memory limit. See: http://discussions.apple.com/thread.jspa?messageID=8340066&#8340066 and http://discussions.apple.com/thread.jspa?messageID=8273626&#8273626

regards, Erik.

Reply

Answer 5

Jason Jones3 Author

Level 1

138 points

Dec 9, 2008 6:15 AM in response to DrNik

It happens pretty consistently now, even after a cold reboot, etc. I haven't tried another project (I'm smack on deadline with this one, OF COURSE!), but will obviously do that immediately. I suppose 4GB is perhaps not enough memory these days? Is that possible on a Quad-core behemoth?

Cheers, and thanks for your help!

J

Reply

Answer 6

Dec 9, 2008 6:44 AM in response to Jason Jones3

I'm curious to know what your activity monitor (Applications/Utilities) says about your memory useage both before and after the project is opened.

Reply

Answer 7

Jason Jones3 Author

Level 1

138 points

Dec 9, 2008 10:11 AM in response to John Buehler

I'm happy to have finally introduced a Topic in LP Discussions that is authentically arcane! Of all the available Google listings on "heap zone," mine, created yesterday, is fifth from the top! That's obscure.

OK, so assuming this was a memory-inadequacy issue, I put in 2GB additional RAM, for a total of 6GB. Absolutely made no difference. So I am certainly willing to try the Activity Monitor approach.

When you ask what the status is both before and after opening the project, do you mean AFTER booting Logic, but before opening this project?

And what am I looking for, precisely? Thanks!

J

Reply

Answer 8

Larry Mal

Level 2

369 points

Dec 9, 2008 10:43 AM in response to Jason Jones3

I will start this by saying that I don't know what the "heap zone" is, but I'm going to make a couple of suggestions anyway. I've been watching the thread, and it was clear to me that more RAM wasn't going to solve the issue, but no harm done. If you are, though, getting close to using 3.5 GB's of RAM (allocated to Logic) then it will get unstable, but more won't help it.

Are you able to know how much RAM you are using at any one time? Activity Monitor will tell you how much you are using, as well as what is using it. I also use a litte app called Menu Meters which hangs on the upper bar and always tells me how much I'm using and what's free at any given time.

Also, is the RAM checking out as OK? You can find this out by simply opening "About this Mac", and going to "Memory", and you should see it say "OK". There are obviously more advanced ways to do this, but that's a start.

Also, and this is just a suggestion, you may want to look into another program I use called Leopard Cache Cleaner. It will provide still more RAM testing, as well as clear your caches and do a little thing it calls "Optimize Free RAM". I know you don't usually need to clear caches with Mac OS, but this time it seems like you may want to do so. Optimizing the RAM is another possible thing that could help and won't hurt, anyway. LCC also has a lot of other diagnostics that may or may not help you. You can get it here, among other places:

http://www.versiontracker.com/dyn/moreinfo/macosx/16494

Also, did you do the extended hardware test that is possible by booting up from your OS install disk? This seems like the time to me.

Just some thought, I hope any of it helps. Unfortunately I have no idea what the problem is. Good luck, L

Reply

Answer 9

Jason Jones3 Author

Level 1

138 points

Dec 9, 2008 10:44 AM in response to John Buehler

Nice job on the Activity Monitor thing: Logic running a smallish project leaves 3GB open. Logic running a gargantuan project leaves ... 3 GB open.

Logic running THIS project used all but 1.6GB of available RAM, even though I've frozen some sixty tracks. Solution: REMOVE BFD and Omnisphere from the three or four tracks where they remained, even though muted and frozen, and voila, 3GB of memory once again available.

Heap Zone. May I never hear that term again. Cheers!

J

Reply

Answer 10

Jason Jones3 Author

Level 1

138 points

Dec 9, 2008 1:13 PM in response to Larry Mal

Extremely helpful! Thanks very much.

While monitoring my memory use in Activity Monitor has helped me reduce the load by unplugging several no longer necessary plug-ins (BFD, Omnisphere), I am still having some issues that are clearly memory related. I will find the cache cleaner and do the hardware test as well.

Thanks!

J

Reply

Answer 11

Larry Mal

Level 2

369 points

Dec 9, 2008 1:16 PM in response to Jason Jones3

Try Menu Meters too- it shows how much RAM you're using as you go. Very helpful. Good luck, L

Reply

Answer 12

Jason Jones3 Author

Level 1

138 points

Dec 13, 2008 9:38 AM in response to Larry Mal

Larry -

Just great advice all the way around: my new, handy Menu Meters tell the story, since this was obviously a RAM cache issue. I had never even heard of clearing memory cache, but once I did these "heap zone" errors stopped completely.

To to anyone else that is getting an error code -108 message regarding insufficient room in the heap zone, this is an indication that there is not enough space in whatever RAM you're using to complete whatever the command was that gave rise to the error message. Clearing the RAM cache, by using Leopard Cache Cleaner for example, solves the problem.

Cheers!

J

Reply

Answer 13

Larry Mal

Level 2

369 points

Dec 13, 2008 10:03 AM in response to Jason Jones3

Awesome! I was reaching there- glad it worked!

Reply

Answer 14

jessrho

Level 1

0 points

Dec 14, 2008 7:34 PM in response to Jason Jones3

HELP?!
I got the -108 error message today too on my most important project in Digital Performer. I got up to work on my project this morning and it wont even let me open my project. Hmmm..., so confused. I tried using the Leopard Cache Cleaner to optimize the ram but still can't open my project. Can anyone help me? Pretty troubled about it. Thanks

Reply

Answer 15

Jason Jones3 Author

Level 1

138 points

Dec 14, 2008 8:52 PM in response to jessrho

Well, my sense is that you want to clear your RAM, as opposed to optimizing it. I noticed when I originally opened LCC that I had an abundance of choices regarding which caches to clear; because I was so freaked out about these constant -108 messages, I selected ALL. I cleared every cache on my machine. Once I had restarted, MenuMeters, an application I downloaded at the same time I got LCC, let me know right away that the free memory available once the project was reopened, had jumped from a scant 1.6GB to close to 4GB. Same project, same number of memory intensive instruments (BFD, VSL, etc.).

Reply