Opened 12 years ago

Closed 12 years ago

#2562 closed Bug (invalid)

Checking large torrents results in huge swap-file

Reported by: Tantali Owned by: livings124
Priority: Normal Milestone: None Set
Component: Mac Client Version: 1.76+
Severity: Normal Keywords:
Cc:

Description

When checking a large torrent (larger than 1GB) the system becomes unresponsive due to an ever increasing swap-file. Verifying large torrent(s) results in a swap-file of 2-3GB on my Macbook Pro, which has 2GB ram (500MB free before starting transmission).

If I remember correctly, verifying around 600 torrents smaller than 300MB didn't cause this (or at least not as much).

This has been around since release 1.75 I think, maybe even earlier. And is still present in the most recent nightly r9485

Change History (4)

comment:1 in reply to: ↑ description Changed 12 years ago by Tantali

Replying to Tantali:

(500MB free before starting transmission)

And with swapfile smaller than 64MB

comment:2 Changed 12 years ago by livings124

Is there anything we can do about this, as app developers?

comment:3 Changed 12 years ago by Tantali

I have no idea...

I don't know whether you see this as normal behavior or as a memory leak.

I just wanted to let you know, as it strikes me as a little bit odd...

When verifying a single torrent of approximately 3,5 gig, the swap-file starts increasing immediately, which means the system is unresponsive throughout the entire verification and at the end of the verification it's recommended to restart Transmission, unless you've got a lot of time...

3 gigs of ram usage for verifying a single torrent... doesn't seem normal to me.

comment:4 Changed 12 years ago by livings124

  • Resolution set to invalid
  • Status changed from new to closed

Using a lot of memory when verifying data is out of our controls. Not much that can be done.

Note: See TracTickets for help on using tickets.