Not sure if this is the right place to report this and I know it's still not even officially out yet and it's possible the transmission developers don't even have it installed yet but I'm getting a slow memory leak while using Transmission the first dev build of Mavericks.
Below are my notes on the issue as well as a screenshot:
1) Seems to occur only or mainly when actively transferring
2) Doesn't seem to matter how many items are transferring or what size they are
3) Steady increase (~0.6MB every 2 second refresh)
4) Happens on both 2.77 and the latest nightly build
5) Continually ads while seeding (I've let it run up over 2GB ram a few times)
6) Does NOT free ram if you stop transferring
Computer info:
Macbook Pro 2010 13"
2.4 GHz Core 2 Duo
8GB ram
OS X 10.9 (13A476u)
Memory Leak Mavericks
Memory Leak Mavericks
- Attachments
-
- Region capture 1.png (242.29 KiB) Viewed 9984 times
-
livings124
- Transmission Developer
- Posts: 3142
- Joined: Fri Jan 13, 2006 8:08 pm
Re: Memory Leak Mavericks
By any chance would you be able to run Instruments on it to get more information on this?
Re: Memory Leak Mavericks
Sure, I suppose I could if I was instructed what to run.livings124 wrote:By any chance would you be able to run Instruments on it to get more information on this?
Also just another note. Developer Preview 2 came out today and the memory leak remains but also a bunch of the icons seem to be rendering as just a black boxes, I've reinstalled transmission and it still appears but I'll hesitate to call it a bug for sure until I check it on my other computer.
Also sorry for taking so long to reply.
Edit: Getting the same square blocks on my other computer.
- Attachments
-
- Region capture 1.png (79.25 KiB) Viewed 9906 times
Re: Memory Leak Mavericks
Hey guys,
I finally had the time to run Instruments on a nightly source (#7927) on OSX 10.9 beta 2. Memory allocation and release works as expected. I had Transmission running for about 27 minutes. After 27 minutes, Transmission allocated a total of 2.81GB and properly released it again so that live memory stayed around 15 MB on average, which looks fine to me.
The only leaks I saw happened every time a torrent was added or removed from Transmission, but those leaks were just a few bytes in total.
OSX however reported that Transmission would require a total of roughly 383 MB after 27 minutes of use, which doesn't fit my observations in Instruments. This makes me guess that the source of this problem lies with Mavericks' new memory management. I think it doesn't properly release memory that has been deallocated, it seems to keep it as inactive for Transmission and doesn't release it completely even if another app requires the memory. This could either be expected behavior to speed up future memory allocations, or it might be a bug in Mavericks. It might even be per design at this point to be able to properly test how Mavericks' new memory compression technique works in low memory situations and it might change in the future as the public release of Mavericks comes closer later this year. I see a very similar problem with XCode and other applications that constantly allocate and deallocate a huge amount of memory.
I finally had the time to run Instruments on a nightly source (#7927) on OSX 10.9 beta 2. Memory allocation and release works as expected. I had Transmission running for about 27 minutes. After 27 minutes, Transmission allocated a total of 2.81GB and properly released it again so that live memory stayed around 15 MB on average, which looks fine to me.
The only leaks I saw happened every time a torrent was added or removed from Transmission, but those leaks were just a few bytes in total.
OSX however reported that Transmission would require a total of roughly 383 MB after 27 minutes of use, which doesn't fit my observations in Instruments. This makes me guess that the source of this problem lies with Mavericks' new memory management. I think it doesn't properly release memory that has been deallocated, it seems to keep it as inactive for Transmission and doesn't release it completely even if another app requires the memory. This could either be expected behavior to speed up future memory allocations, or it might be a bug in Mavericks. It might even be per design at this point to be able to properly test how Mavericks' new memory compression technique works in low memory situations and it might change in the future as the public release of Mavericks comes closer later this year. I see a very similar problem with XCode and other applications that constantly allocate and deallocate a huge amount of memory.
Re: Memory Leak Mavericks
A little update on this memory leak issue in Mavericks:
It took me a while to notice, but the leak doesn't occur when all windows are closed and Transmission is running "headless", as in "just the dock icon is visible, nothing else".
So whatever is happening, it seems to have to do with changes in Maverick's drawing routines, or so I think.
It took me a while to notice, but the leak doesn't occur when all windows are closed and Transmission is running "headless", as in "just the dock icon is visible, nothing else".
So whatever is happening, it seems to have to do with changes in Maverick's drawing routines, or so I think.
Re: Memory Leak Mavericks
The leak seems to be gone with Mavericks DP3. I think you can consider this issue closed - for now.
Re: Memory Leak Mavericks
Problem seems to be back in DP6. Is it just me or is anyone else experiencing this again?