Change By: Libero Scarcelli (18/Feb/15 4:09 AM)
Description: On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze

Tested on a single core Windows 2008 R2 machine
 running Jenkins 1 . 596 .  The problem *seems* to get worse after installing the latest core (1 .  with 599) due maybe to the latest log format changes (?)

With
 multiple cores it *might* be possible to increase the number of rows to be shown without any issue. However, I think loading build logs at this stage is CPU consuming
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to