#6 Desktop Notifier Runaway Memory - Notify.io

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#6 new

Desktop Notifier Runaway Memory

Reported by digerata | July 11th, 2010 @ 04:25 PM

I'm noticing greatly increased memory usage and cpu spikes. I'm fairly sure the memory usage is new with the latest release. Today I had not much running and was using more memory then normal. I pulled up activity monitor and saw that NIO was using up a ton. I've never had to do this with the notifier before...

The CPU spikes every 30 seconds or so. At rest, the CPU is around 8%.

After further monitoring after restart, I checked the Console and found these messages:

7/10/10 7:44:12 PM Nio[41804] conn: <NSURLConnection: 0x23b877a0, http://guide.opendns.com/?url=api.notify.io%2Fv1%2Flisten%2F50db9ae...>
7/10/10 7:44:12 PM Nio[41804] connection finished

There are anywhere from 5 to 16 of these output every second. The notifier's current memory usage after just a few hours is at 340 MB.

Looks like maybe a DNS problem is exacerbating a connection leak. Although, I see that after a restart the problem is gone. Maybe the DNS failure caused a redirect to OpenDNS's default host not found page which the application cached and continued to reuse even after DNS was fixed?

I've attached two screen shots and a profile of Desktop Notifier.app when it had 1 GB used.

screen-shot-2010-07-09-at-121438-pm.png 18.1 KB
screen-shot-2010-07-09-at-121515-pm.png 17.4 KB
sample-of-nio.txt 73.3 KB

Comments and changes to this ticket

progrium (at gmail) July 12th, 2010 @ 11:36 PM
- Tag set to “nio”
- Assigned user set to “progrium (at gmail)”
Thanks to help of Santiago (http://github.com/DFectuoso/Nio), we've made something that's quite a bit more resource friendly. I'm attaching a build of the app for you to try and reproduce.
- nio.zip 3.2 MB
You flagged this item as spam.
digerata July 14th, 2010 @ 09:04 AM
I've only been running this since yesterday. But it already shows indication that the problems are resolved. Its current memory usage is at 16M. Compared to 350M used after 24 hours, previously.

I do still wonder about the potential DNS issues, however. I haven't had a failure yet.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.