Left rocket burning for eight hours - came back and physics is broken

[THX1138]

I think I made a mistake. I think the change in orbit I was seeing was due to the oscillation of my craft attached to the asteroid.

I have a strange problem. I've had a bad time trying to push a class E asteroid out of solar orbit - I was forced to leave the rocket at no more than 10% thrust (prograde) to prevent it spinning and I left it minimised like that for about eight hours. When I came back I found that the opposite side of the orbit is getting smaller not larger! Worse still, it carries on doing it after I switch off the thrust! The orbit is changing even though no forces are being applied!

Save file

Output log

OS: Win 7 64-bit

Mainboard: Gigabyte GA 790FXTA-UD5

CPU: AMD Phenom II 965 X4

RAM: OCZ Black Ed 2x2GB DDR3-1600 + Corsair 2x2GB DDR3-1600

Graphics: Sapphire HD 5770 1GB GDDR5 x2

DVDRW : LG-GSA-4167B

Sys Drive: OCZ Vertex 2, 60 GB

Data Drives:

PSU: Thermaltake 705w / 700W +3.3V 30A = +5V 28A = 4x +12V 18A

KSP 0.9, as updated by Steam

Edited January 8, 2015 by THX1138

[Claw]

I have found that leaving KSP open for extended periods of time can cause all kinds of problems. I'd say 8 hours of burn falls into that category.

Your log file does indicate some of the physics calculations broke down, but there's not a clear cause in there. Also, the claw part seems to be a bit buggy at times.

Your save file wasn't coming up on filedropper, so I can't guess much more than that.

Cheers,

~Claw

[wibou]

You do know you can "force" some time warp while burning by pressing <Modkey> + <WarpKey>, right?

Although, if you had spinning problem, time warp could have resulted in a disaster as well

[vexx32]

In all honesty, even the most thoroughly-tested professional applications and games (say, for example, a professional suite like Photoshop or those other Adobe tools) are generally not designed to be used for eight hours straight. I can't say there's really much you could do to prevent this happening -- sooner or later, a tiny and unrecognisable memory leak can become an immense problem.

Judging from the log files, you're getting stack overflows and the like, so there's not a lot I can see to really help you. KSP simply isn't really designed to be left running for 8 hours.