Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#1318 closed Bug (fixed)

transmission eats all resources after incorrect JSON/RPC query

Reported by: spry Owned by: charles
Priority: Normal Milestone:
Component: libtransmission Version: 1.34+
Severity: Major Keywords:
Cc:

Description

%CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND 99,0 51,3 1069336 1067428 ?? Rs 23:50 55:13,35 /usr/local/bin/transmission-daemon

This issue raised after incorrect JSON/RPC query. Also, it stopped responding to any RPC queries.

Change History (14)

comment:1 Changed 11 years ago by spry

Forgot to mention that it is Transmission 1.34+ (6830)

comment:2 Changed 11 years ago by spry

At normal operation it eats ~80% CPU and 1% of RAM. My server has 2,2Ghz CPU and 2Gb of RAM. I don't believe that it is due to debug build, it's way too high.

comment:3 Changed 11 years ago by charles

I'm not seeing anything remotely like that. Could you profile your build to see where the daemon is spending its time?

comment:4 Changed 11 years ago by spry

If you'll explain how to do that, I'll do it :)

comment:5 Changed 11 years ago by charles

well first, what platform are you on?

comment:6 Changed 11 years ago by charles

actually, if you want to drop by #transmission in irc, that's probably a faster way to do back-and-forth messages ;)

comment:7 Changed 11 years ago by spry

Well, seems that the time zone difference (I'm in Ukraine, +2 GMT) makes our direct contact hardly possible. Currently, 6.2% of CPU. So, as far as I understand, The >60% CPU load is connected with the bug I've posted about invalid RPC request processing. I'm sorry that I can not help a lot in debugging, since I'm skilled win32 developer, not *nix developer :)

comment:8 Changed 11 years ago by charles

  • Component changed from Daemon to libtransmission
  • Keywords backport-candidate added; daemon cpu mem usage removed
  • Milestone changed from None Set to 1.40
  • Status changed from new to assigned

comment:9 Changed 11 years ago by charles

  • Resolution set to fixed
  • Status changed from assigned to closed

looks like we're getting stuck in an infinite loop when we try to serialize corrupt utf-8 strings to json.

fixed in r6851.

comment:10 Changed 11 years ago by charles

  • Summary changed from transmission daemon eats all resources to transmission eats all resources

Changing subject from daemon' to transmission'... this bug applies to the OS X and GTK+ clients too.

comment:11 Changed 11 years ago by charles

  • Severity changed from Normal to Major

comment:12 Changed 11 years ago by charles

  • Summary changed from transmission eats all resources to transmission eats all resources after incorrect JSON/RPC query

comment:13 Changed 11 years ago by charles

  • Milestone 1.40 deleted
  • Version changed from 1.34 to 1.34+

comment:14 Changed 11 years ago by charles

  • Keywords backport-candidate removed
Note: See TracTickets for help on using tickets.