another shell bug

[cekuhnen]

looks to me the shelling has some serious problems in Fusion

https://drive.google.com/file/d/0Byzv_NlyKp_2ak1sXy1NYkQzeFE/view?usp=sharing

If I shell side A (gray) it works, if I shell side B (fgreen) it freezes Fusion.

Both sides were originally one body I just split it at the center

If I shell the complete body and then split the sides I end up with two shelled sides.

So the model is fine the shell code is not.

[innovatenate]

I found that if you wait long enough, the shell works like a dream! See the attached file for reference.

How long did you let the Shell compute before Force Quitting?

Cheers,

[cekuhnen]

I waited for some time and then simply quite.
In the finder it was listed as not responding.

[innovatenate]

When I test this, I see that the CPU usage maxes out for this operation.This is the reason you're seeing the "not responding" message in the activity monitor. This can happen for any application, including the Finder. See example in below link.

https://discussions.apple.com/thread/2690211

In this case, there is not much to do but wait and see what happens. As long as you're not out of memory/RAM, the best bet is to wait and see if the command finishes or the memory resources become exhausted. If you find that you start paging, then I would probably Force Quit and try going another way with a different set of features. 

I note that the shell operation seems to be so much faster if you shell the body prior to splitting it. Is there a reason why this approach is less desirable? 

Cheers,

[cekuhnen]

it is not less desirable but sometimes it does not work.
thats then when I split and then shell.

normally you want to shell and then split.