Memory Leak?

[takuhii]

No sure what's happening here, but I have Terminal Notifier running in 5 Terminal windows, but it is consuming GBs of memory, so much so my Macbook stops working...

[julienXX]

Which version do you use?

[takuhii]

It updated over home brew this morning, but I believe it is version 1.7.0

[julienXX]

Could you try this version https://github.com/julienXX/terminal-notifier/releases/tag/1.7.1 and tell me if it's better? (Not yet available via homebrew)

[takuhii]

ok, I'll give it a whirl and keep you posted

Thank you :)

[julienXX]

I managed to reproduce the issue when using -reply and no action is taken for example, this keeps terminal-notifier running and eating RAM.

[frdmn]

Same problem over here. 15 GB physical memory + 30 GB swap:

[julienXX]

@takuhii @frdmn what did you do with terminal-notifier in order to get this? Launch notifications manually, via a script... ?

[takuhii]

You're 1.7.1 update did the trick @julienXX I've had no more "leaks". The only thing I had to do after I applied it was reboot my Mac... I am invoking Terminal Notifier via a Script BTW ;)

[julienXX]

@frdmn do you have the issue under 1.7.1?

[frdmn]

@julienXX I was using the homebrew / Ruby wrapper of the binary. How can I extract just the terminal-notifier binary out of this .app bundle?

When I just copy it from Contents/MacOS/terminal-notifier I get the following error message:

2016-10-05 15:52:58.476 terminal-notifier[18802:3271692] No Info.plist file in application bundle or no NSPrincipalClass in the Info.plist file, exiting

[julienXX]

@frdmn 1.7.1 is available via homebrew or you can download the executable here https://github.com/julienXX/terminal-notifier/releases/tag/1.7.1

[frdmn]

@julienXX Ah great, just got the update in brew. I'm not sure how to reproduce the problem precisely, but for now none of the processes are stuck and memory looks good as well. 👍

I'll let you know if the problem still occurs with 1.7.1

[julienXX]

Great, I close the issue, feel free to re-open it if needed.