1Password Mini Using Huge Amounts of Memory (5GB)

LoneStarX

I saw a closed post about this problem from back in April 2014. Apparently it has not been resolved yet.

Ben

Hi @LoneStarX‌

I'd be very interested to find what might be causing this problem for you.

Could you please take a screenshot of what 1Password Mini looks like for you when selected in Activity Monitor's Memory tab? You can find Activity Monitor in your /Applications/Utilities folder (or via Spotlight). For reference, here is what mine looks like:

ilsa

Hi, I just wanted to comment that I recently noticed the same thing. I'm thinking there is a memory leak somewhere because I almost never reboot my computer, and I use 1password constantly. Unfortunately I didn't have the presence of mind to take a screenshot before I killed it, but my 1password_mini was sitting at 2.5GB. I don't recall how much the main 1password process was using. I'll try to remember to take a screenshot next time.

littlebobbytables

Please do @ilsa‌ I'm sure the devs would be interested.

LoneStarX

Just caught it at 4.5GB but didn't see your post until after I closed the app. I will get a screenshot the next time it gets up there and will eMail to you.
It happens often enough. Standby ...

rickfillion

Hi @LoneStarX and @ilsa,

I'd be curious to know what versions of 1Password you're using. We've fixed many leaks in the last few releases. There are probably still others (sometimes they hide really well).

If you're comfortable on the terminal, I'd be curious to get the output of heap $PID where $PID is the process id of 1Password mini. It'll give us a rough idea of where the leaks could be.

Rick

LoneStarX

Already creeping up...
1Password version is 5.1 Mac Store.

I tried to attach a text file containing the heap dump but your forum would not let me attached. Give me an eMail address to send to please.

Jasper

Hi @LoneStarX,

Please email the text file, along with a link to this discussion to: support+forum@agilebits.com

Thanks! :)

rickfillion

Hi @LoneStarX,

Thanks for the heap output. As mentioned in the email it clearly showed a leak of two object types (I suspect that when we fix the one, the other will fix itself). From here it shouldn't be too difficult to fix up.

Rick

ref: OPM-2855

LoneStarX

Glad I could help. I look forward to the update.

littlebobbytables

and thank you for helping pin down where it was happening @LoneStarX. Often data from the instance where it is going wrong is invaluable depending on how easy or hard it is to replicate on another machine.