[aerospain]

Dear all,

I'm facing a strange behavior by paraFoam when clipping my 3D domain. It didn't occur until recently, when I had to run some software updates that involved Qt.

I explain step-by-step:
1) I run paraFoam from my case directory. And, load the solution with the following options activated: 'Cache Mesh', 'Interpolate Volume Fields' (both by default), and 'Skip Zero Time' (to save some time in loading. It's a steady simulation and deactivating this option doesn't make any difference in the faulty behavior)

2) I clip in X, with the default 'Origin' selected (9.75, 0, -0.000329971313476562), and it goes fine. With the 'Inside Out' & 'Crinkle clip' options selected too.
** At this moment, I only have two messages in my terminal:
>>> Gtk-Message: Failed to load module "overlay-scrollbar"
>>> I/O : uncollated

3) I clip in Y, with same 'Origin'. It goes fine. With the 'Inside Out' & 'Crinkle clip' options selected too.

4) I clip in Z, with same 'Origin'. Still, everything ok. With the 'Inside Out' & 'Crinkle clip' options selected too.

Now, to avoid showing tetrahedrons in the clips, I want to 'Use VTK Polyhedron'. Therefore, I select that option and reload the case, with the clip deactivated, only the 3D block is activated in the 'Pipeline Browser' tree. Everything ok, ParaView is still running and no message shows up in the Terminal.

1) I clip in X, with no options selected. And everything goes ok.

2) But, when I try to clip in Y, ParaView shuts down, and I get the following message in the Terminal:
>>> terminate called after throwing an instance of 'std::bad_alloc'
>>> what(): std::bad_alloc
>>> Qt has caught an exception thrown from an event handler. Throwing
>>> exceptions from an event handler is not supported in Qt. You must
>>> reimplement QApplication::notify() and catch all exceptions there.
>>> Aborted (core dumped)

I have installed the latest Qt version from the official webpage (https://wiki.qt.io/Install_Qt_5_on_Ubuntu), using the latest version 5.10.1

Any ideas, please?

C.