Using SolveSpace master at 4465bc0, built with "cmake .. -DCMAKE_BUILD_TYPE=Release"
I originally observed this with a version where I had cherry-picked 9cf1a09 and a5ffd9d from https://github.com/whitequark/solvespace/issues/147 but the same problem also occurs in the "plain vanilla" version above.
It's the usual model, alt13/an-top.slvs from https://gitlab.com/anelok/mexp.git
this time at commit cb75c4a1.
I'm trying to shift an assembly a little, which affects various later groups. Unfortunately, this makes the computation time explode.
Here are the steps that lead to the problem. Cumulative CPU times (on Q6600 at 2.4 GHz) are according to "top".
-
solvespace an-top.slvs -> 13 s (Generate::ALL took 5322 ms, Generate::DIRTY took 5143 ms)
-
show occluded lines, select g019-aaa-minus, enable "show" -> 16 s
-
change 1.50 (lower left corner) to 1.25 -> 17 s
-
activate g027-an-screw-placement -> 25 s (DIRTY took 5182 ms)
-
activate g028-sk-boss -> 58 s (DIRTY took 33062 ms)
-
activate g029-boss -> ~340 s (DIRTY took 328456 ms), followed by
ALL (for bounding box) took 446 ms
But it continues calculating. Now I'm at 100 CPU-minutes and counting. Virtual memory size is increasing slowly, at about 4-5 kB/s. Physical memory size has increased by almost 50% over the time since activating g029-boss, suggesting that SolveSpace is indeed accessing the memory it has allocated.
Using SolveSpace master at 4465bc0, built with "cmake .. -DCMAKE_BUILD_TYPE=Release"
I originally observed this with a version where I had cherry-picked 9cf1a09 and a5ffd9d from https://github.com/whitequark/solvespace/issues/147 but the same problem also occurs in the "plain vanilla" version above.
It's the usual model, alt13/an-top.slvs from https://gitlab.com/anelok/mexp.git
this time at commit cb75c4a1.
I'm trying to shift an assembly a little, which affects various later groups. Unfortunately, this makes the computation time explode.
Here are the steps that lead to the problem. Cumulative CPU times (on Q6600 at 2.4 GHz) are according to "top".
solvespace an-top.slvs -> 13 s (Generate::ALL took 5322 ms, Generate::DIRTY took 5143 ms)
show occluded lines, select g019-aaa-minus, enable "show" -> 16 s
change 1.50 (lower left corner) to 1.25 -> 17 s
activate g027-an-screw-placement -> 25 s (DIRTY took 5182 ms)
activate g028-sk-boss -> 58 s (DIRTY took 33062 ms)
activate g029-boss -> ~340 s (DIRTY took 328456 ms), followed by
ALL (for bounding box) took 446 ms
But it continues calculating. Now I'm at 100 CPU-minutes and counting. Virtual memory size is increasing slowly, at about 4-5 kB/s. Physical memory size has increased by almost 50% over the time since activating g029-boss, suggesting that SolveSpace is indeed accessing the memory it has allocated.