[Cherokee-dev] Issue 1361 in cherokee: Big files result in 100% cpu load, even after the download has been finished

0 views
Skip to first unread message

cher...@googlecode.com

unread,
May 31, 2012, 10:31:30 AM5/31/12
to cherok...@cherokee-project.com
Status: New
Owner: ----

New issue 1361 by ste...@opengeo.nl: Big files result in 100% cpu load,
even after the download has been finished
http://code.google.com/p/cherokee/issues/detail?id=1361

What steps will reproduce the problem?
1. github dev repo
2. download a huge file
3. observe 99% cpu time, even after the download has been finished.

It seems that when cherokee trace is enabled it is actually 'working' as
expected.

_______________________________________________
Cherokee-dev mailing list
Cherok...@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

cher...@googlecode.com

unread,
Jun 8, 2012, 6:25:26 AM6/8/12
to cherok...@cherokee-project.com

Comment #1 on issue 1361 by mehmetal...@gmail.com: Big files result in 100%
cpu load, even after the download has been finished
http://code.google.com/p/cherokee/issues/detail?id=1361

i think duplicate of r1359

cher...@googlecode.com

unread,
Jun 8, 2012, 6:28:16 AM6/8/12
to cherok...@cherokee-project.com

Comment #2 on issue 1361 by mehmetal...@gmail.com: Big files result in 100%
cpu load, even after the download has been finished
http://code.google.com/p/cherokee/issues/detail?id=1361

i think duplicate of id1359

cher...@googlecode.com

unread,
Jun 8, 2012, 12:02:43 PM6/8/12
to cherok...@cherokee-project.com
Updates:
Status: Duplicate
Mergedinto: 1359

Comment #3 on issue 1361 by ste...@konink.de: Big files result in 100% cpu
load, even after the download has been finished
http://code.google.com/p/cherokee/issues/detail?id=1361

You are right. I should have spotted this myself. (Was under my other
account.)
Reply all
Reply to author
Forward
0 new messages