BUG???: Memory hog on Mac

After downloading the two most recent betas of Proclaim, I've been having problems with Proclaim max-ing out my computer memory. I have a 5 month old MBP (2 GHz i7 with 4GB of 1333 MHZ DDRR3 memory running Lion 10.7.2).

Basically when I open up Proclaim and started moving through my worship sequence, I'll click on a song and Proclaim will suddenly snag a 1 GH of memory and leave me stuck waiting for 5 min until I can force quit Proclaim. This seems to be the case, even when Proclaim is running without any other active application.

I never had any problems like this with any of the earlier betas, and I don't think it happens in Windows. (I'll have to test this...)

Has anyone else had a similar experience on a Mac?

Thanks.

Find more posts tagged with

Comments

Hunter Clagett

There have been some issues with memory leaking from the application. We have committed some fixes for these.

Are you still having the same troubles after updating to Version 1?

Thanks,

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

After installing v1.00, the worst of the memory problems seem to have decreased. I will do so more testing through normal and see if they have continued, and to what extent.

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/320588#Comment_320588

Hunter,

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

Marc

Pastor Rickabaugh

https://community.logos.com/discussion/comment/321408#Comment_321408

Pls. delete all the accidental reposts. Sorry about that.

TCBlack

https://community.logos.com/discussion/comment/321413#Comment_321413

Pls. delete all the accidental reposts. Sorry about that.

It's not your fault. See Forum Posting => Error

Pastor Rickabaugh

https://community.logos.com/discussion/comment/321430#Comment_321430

:-) Thanks for the info. It made me look an internet novice. I even tried to delete them, but it didn't work.

Hunter Clagett

https://community.logos.com/discussion/comment/321490#Comment_321490

Thanks for your help with this, Marc! I have submitted your information to our developers for review.

Thanks,

Jeffrey Mashaw

https://community.logos.com/discussion/comment/321397#Comment_321397

The memory "max-ing" out problem still remains. In fact, it basically locked up Proclaim and them it crashed! This was on my 2-3 year old iMac with 4 GB.

658350.Proclaim.log

Just so you know, I am using HD "motions" (16x9) as backgrounds. Didn't know if that would be a factor.

I think I am having the same, or a similar problem. I have 3 HD motion backgrounds uploaded and selected in a decent sized presentation, and I have had this program crash on me 5 times at least all in the same way. I am simply trying to navigate around within a song or between 2 different songs, then Proclaim tries to re-render the preview frames, then it freezes and crashes. When I looked at my Activity Monitor Proclaim had used up all 1.3gb of the free ram.

I was hoping to use this Sunday, help!

3652.Proclaim_Crash.txt

3051.Proclaim.log

Scott Alexander

https://community.logos.com/discussion/comment/321741#Comment_321741

We have a significant memory leak for Mac fix slated to release Monday. Sorry it's not in time for this Sunday.

David Price

https://community.logos.com/discussion/comment/322056#Comment_322056

So, am I getting the story right that because of this leak, Proclaim is going to essentially be useless to us tomorrow?? That is not a good thing to find out today as we're trying to put in slides. As much as I like the idea of Proclaim, I have had too many issues with it running sluggish and not syncing correctly to feel it is dependable on a regular basis, especially now that it's out of Beta and still having problems. I really want to like this, but this is going to cause a late night and early morning for coming up with plan B (and that's after wasting a half hour wrestling with it trying to get it to respond before finding this thread). Not angry and I do understand issues occasionally happen, but definitely wrestling with disappointment and frustration with this program.

Tony Silveira

https://community.logos.com/discussion/comment/322056#Comment_322056

I hope it works... It gets to a point where the computer freezes. I am using a little workaround by using a little APP called FreeMemory that is resident on the top bar. Whenever it goes on red I click it. Yesterday I had to force quit Proclaim and the weird thing was that I couldn't even do it...

Pastor Rickabaugh

https://community.logos.com/discussion/comment/322056#Comment_322056

Scott,

Just in case you haven't seen my other posts...

I DL'ed the new update today. While the memory leak issues are BETTER on my Mac, they're are far from "fixed". It's been so bad on OS X Lion today, I rebooted and started using Proclaim on my W7 partition (It Windows 7, I have not problems with Proclaim). Honestly, this version of Proclaim for Mac is less functional in terms of reliability than one of the first betas.

Please fix the memory problems before Sunday! They're driving me nuts!

Scott Alexander

https://community.logos.com/discussion/comment/324186#Comment_324186

Marc - Any feedback on how you were using the application which caused it to run out of memory would be helpful. Currently we're looking into a leak related to customizing slides. Are you doing a lot of customization?

Pastor Rickabaugh

https://community.logos.com/discussion/comment/324444#Comment_324444

So, I just tried to reproduce the bug again. Proclaim for Mac more or less behaves itself when I'm NOT working with songs. I should start by saying I use HD videos/motions with Proclaim. At first, everything seems fine. I can customize a slideshow with Powerpoint jpegs, no problems. But if I click on a HD motion song (according to my free memory app or activity monitor) 300-400 MB of memory is grabbed. Not too bad until I click on another song...another 300-400 MB of mem. is drawn down...Then, on the next song, the same thing, etc. By the 3rd or 4th song, I think file swapping begins in force (with only 25 MB left, that's no surprise!), Proclaim bogs down dramatically (effectively locks up) and sometimes crashes.

I have a 4 month old BTO MBP with 4 GB, i7 processor, 7200 rpm HDD, Lion.