Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash due to CHECK(v2.WillKeepPart(part2)) #3339

Closed
rnlahaye opened this issue Mar 13, 2022 · 3 comments
Closed

Crash due to CHECK(v2.WillKeepPart(part2)) #3339

rnlahaye opened this issue Mar 13, 2022 · 3 comments

Comments

@rnlahaye
Copy link
Contributor

I recently experienced a crash after decoupling. Here is the relevant section of the logs (the full error log is attached):

I0312 15:48:34.647652 41928192 ksp_plugin_adapter.cs:1316] Reporting collision with collider SC-ENG-MOUNT-SKELETAL-M-Collider3 (0)
I0312 15:48:34.647687 41928192 plugin.cpp:564] Collision between ROT-RingDecoupler (D297F2F1) and ROT-BalloonTank-New (20C61FFF)
    @        0x5e1d26d5f  google::LogMessageFatal::~LogMessageFatal()
    @        0x5e1d23009  google::LogMessageFatal::~LogMessageFatal()
    @        0x5e19ee7df  principia::ksp_plugin::internal_plugin::Plugin::ReportPartCollision()
    @        0x5e1914998  principia__ReportPartCollision
F0312 15:48:34.647722 41928192 plugin.cpp:571] Check failed: v2.WillKeepPart(part2) ROT-BalloonTank-New (20C61FFF) will vanish

This seems to be ksp_plug/plugin.cpp:571.

Here ROT-BalloonTank-New is the rocket and ROT-RingDecoupler is the decoupler. I accidentally decoupled the wrong side of the decoupler (the rocket was released but the decoupler remained attached to my probe). When I subsequently detached the correct side, the decoupler flew off and eventually crashed into the rocket, resulting in the CHECK-failure.

I will try to get a journal.

@rnlahaye
Copy link
Contributor Author

I was unable to get a journal.

@pleroy
Copy link
Member

pleroy commented Apr 25, 2022

Might be a duplicate of #3219.

@pleroy
Copy link
Member

pleroy commented Dec 18, 2022

Closing as we have not heard of this bug after #3349.

@pleroy pleroy closed this as completed Dec 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants