-
Notifications
You must be signed in to change notification settings - Fork 511
Assertion failed: hm.v != t->h.v. #435
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
Comments
Does it work in commit 406c55e ? |
Yes, it does, as you can see the model is quite heavy even for my beefy machine:
|
So, since you can't share the file, it's going to be pretty painful, because the bug is in bd84bc1 but I have no idea where. I would need, at least, a backtrace to the assertion, plus you'll need to add a |
Can I send a file privately to your email from GitHub account to make things easier? |
My email is whitequark@whitequark.org. But I don't think you can send emails via GitHub itself. |
Not through GitHub itself, I meant you have an email specified in your profile. |
I just had this crash too (on cb0fdb1) with a simpler-sounding model, would you like it or do you already have enough info? Backtrace:
|
Simpler is always nicer. |
Here you go: http://misc.tomn.co.uk/repro_435.slvs Go to the sketch labelled "THIS ONE" and add a point to the quadrilateral. |
I don't quite understand why yet, but adding +1 in std::tie(it, inserted) =
remap.insert({ { in, copyNumber }, { (uint32_t)remap.size() + 1 } }); solves it for files I have. This replicates the behaviour of |
You're absolutely right. I reviewed this code more than once, wrote tests for it, and still missed it somehow... |
Thanks everyone, fixed in 49a7f86. |
PSA: all files created in the last 25 days (between bd84bc1 and 49a7f86) are subtly corrupted, with some entities remapped to
It's not entirely clear what the full consequences are. In any case, this is recoverable by removing any entires in |
I've added some code to recover the corrupted files in 02d7f0c. No action is required. If the recovery process causes data loss (which it should not), this will be indicated by the usual "Additional sketch elements were deleted" dialog. |
System information
SolveSpace version: 3.0.0~9ac55f3 (from ppa)
Operating system: Ubuntu 19.10
Expected behavior
Opening model shouldn't crash an app
Actual behavior
Application crashes while opening one of the bigger models I have
Additional information
This is console output during crash:
I would prefer to not share the file, but it includes multiple other files liked into bigger model, some of which also linked with other files.
I was using older 3.0.0 version before and it worked, but can't say confidently when I have opened that exact file last time and what build was installed back then.
The text was updated successfully, but these errors were encountered: