Project

General

Profile

Bug #5201

Each flight spawns new thread at 100% CPU

Added by soreven almost 9 years ago. Updated almost 9 years ago.

Status:
Moot
Severity:
High
Assignee:
-
Category:
Physics
Target version:
-
Start date:
07/02/2015
% Done:

0%

Version:
1.0.4
Platform:
Linux
Expansion:
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

Every time I start a new flight, or revert an in-progress flight (either to launchpad or VAB), a new process thread is spawned which maxes out one CPU core in perpetuity. The threads remain running at max until the main application quits; leaving to the main menu does not halt them. Occasionally, and not readily reproducible, the threads will continue to run even after the main application quits. These stray processes can only be ended by issuing a kill command.

To reproduce:
  1. Start htop to monitor CPU usage, and set it to sort by CPU%. Filter on "KSP" if necessary.
  2. Start KSP.
  3. Note a single CPU thread that is pegged at 100% - 105%.
  4. Load a game (or start a new one) and start a new flight on the launchpad. You don't actually have to go anywhere, or do anything with the ship.
  5. Note a second CPU thread has been spawned, and it is pegged at 100%.
  6. Press Escape, and revert to Launchpad.
  7. Note another CPU thread has been spawned, and it is pegged at 100%. All previous threads remain pegged at 100%.
  8. Repeat last two steps ad nauseum until your CPU has suffered enough.
  9. Quit to main menu. Note that CPU threads remain active.
  10. Exit application. Note that the CPU threads (most of them, anyways) finally stop.
Flight 1.png (1.12 MB) Flight 1.png soreven, 07/02/2015 05:08 PM
Flight 2.png (1.14 MB) Flight 2.png soreven, 07/02/2015 05:08 PM
Flight 3.png (1.15 MB) Flight 3.png soreven, 07/02/2015 05:08 PM
Flight 4.png (1.18 MB) Flight 4.png soreven, 07/02/2015 05:08 PM
Flight 8.png (1.22 MB) Flight 8.png soreven, 07/02/2015 05:08 PM
Flight 13.png (1.2 MB) Flight 13.png soreven, 07/02/2015 05:08 PM
6997
6998
6999
7000
7001
7002

History

#1 Updated by soreven almost 9 years ago

I first noticed this problem in 1.0.3, but it persists in 1.0.4. I am using the x64 binary on Linux Mint 17.

#2 Updated by Squelch almost 9 years ago

Please can you confirm this is an unmodded install?

It would also be appreciated if you could provide some other supporting evidence such as logs. We are unable to confirm the cpu saturation, nor the zombie threads.

For guidance, see the Bug Reporting Guide.

[Edit] A strace of one of the threads would also be useful.

#3 Updated by Squelch almost 9 years ago

  • Status changed from New to Need More Info

#4 Updated by Mesons almost 9 years ago

I can't reproduce this on an unmodded install on Ubuntu 14.04. I see a lot of mods installed in your attached images; the issue probably lies with one of them. Try to remove the mods one by one until the problem goes away, and you'll know which mod is at fault.

#5 Updated by soreven almost 9 years ago

Squelch wrote:

Please can you confirm this is an unmodded install?

It would also be appreciated if you could provide some other supporting evidence such as logs. We are unable to confirm the cpu saturation, nor the zombie threads.

For guidance, see the Bug Reporting Guide.

[Edit] A strace of one of the threads would also be useful.

I apologize, I hadn't seen the Bug Reporting guide. I was able to isolate this issue to a specific mod (KSP Trajectory Optimization Tool). This bug can be closed out.

#6 Updated by Squelch almost 9 years ago

  • Status changed from Need More Info to Moot
  • % Done changed from 0 to 100

soreven wrote:

I apologize, I hadn't seen the Bug Reporting guide. I was able to isolate this issue to a specific mod (KSP Trajectory Optimization Tool). This bug can be closed out.

Thanks for reporting back, and I'm glad you have identified the problem.

Also available in: Atom PDF