[Paraview] [EXTERNAL] Re: Paraview crashing when clipping an openfoam solution

[Scott, W Alan]

Hi Carlos,
As Shawn says, you are running out of memory.  As a guess, this isn’t a hardware issue or ParaView issue, but rather a “too much data in a 5 pound bag” issue.  Here are some thoughts:

  *   Run View/ Memory Inspector.  As you do stuff, watch memory grow.  Does it look like memory is growing until PV dies?
  *   Minimize the size of your dataset.  Although you only have a million cells (rounding), how many variables to you have?  Don’t load (or don’t create) variables that you don’t need.
  *   How many blocks do you have?  If the answer is lots (hundreds?), I believe this creates memory pressure.
  *   Do you have sidesets/ edgesets?  Don’t load these unless needed (as you can see, I don’t know openfoam).
  *   Run top.  How big is ParaView getting?
  *   Try opening your data with no variables loaded.  What is the memory inspector doing?
  *   How much hardware do you have on your computer?  If it’s a new computer with 8 GBytes, that is very different than an old converted machine with .25GBytes.
  *   Try looking at your memory footprint (memory inspector, top) BEFORE applying filters.  Every filter you use increases memory.
  *   Use filters such as slice (i.e., 2d) rather than clip (3d), and contour (2d) rather than clip by scalar.  What I mean here is to create a surface, rather than a solid.  Surfaces use less memory.
  *   Don’t volume render.  It really sucks memory.


That’s what I can think of...

Alan

From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Carlos E Manglano-Villamarin
Sent: Monday, March 26, 2018 12:30 PM
To: Waldon, Shawn (External Contacts) <shawn.waldon at kitware.com>
Cc: paraview at public.kitware.com
Subject: [EXTERNAL] Re: [Paraview] Paraview crashing when clipping an openfoam solution

It's me again, I'm sorry,

Problem NOT solved!!! ... Hardware looks ok, software and system handling memory looks good too.

ParaView shuts down if I try to generate a clip with the "VTK Polyhedron" option selected, before and after clipping ...

possible bug??

C.

2018-03-26 16:51 GMT+02:00 Shawn Waldon <shawn.waldon at kitware.com<mailto:shawn.waldon at kitware.com>>:
Hi Carlos,
That error message means that an exception was thrown from a Qt event handler.  The message about reimplementing QApplication::notify() is just to tell you how to catch the exception if you wanted to.  The real problem is the exception.
A std::bad_alloc exception happens when the program tries to allocate memory and fails.  So you need to figure out why you are running out of memory (that is the most likely cause of the error).
HTH,
Shawn

On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin <carlosemanglanov at gmail.com<mailto:carlosemanglanov at gmail.com>> wrote:
Hi everyone!
When I postprocess some simulations, less than 900,000 cells, from openfoam, either opening paraview directly or using the parafoam tool, the program crashes giving me the following error message:

I/O    : uncollated
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.
My OS is Ubuntu 16.04, freshly installed. I was getting the same error with Ubuntu 17.10 which I had installed until last night.
I am looking for info about "reimplementing QApplication" with no luck.
Any suggestions, please?
Carlos

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180326/29003f4b/attachment.html>