Thanks Joachim,

I suspected it was more interesting than “just” a program bug. 

> El 26 mar 2018, a las 21:39, Joachim Pouderoux 
> <[email protected]> escribió:
> 
> Crashes did not occur all the time. It depends on the cell geometry/topology 
> and the slice origin/normal.
> 
> Joachim Pouderoux, PhD
> Technical Expert - Scientific Computing Team
> Kitware SAS
> 
> 2018-03-26 15:14 GMT-04:00 Carlos E Manglano-Villamarin 
> <[email protected]>:
>> Quite interestingly, I have just create a 2D slice in a mesh with 947443 
>> cells, and it has not crashed!! It is showing the "holes" you mentioned 
>> before, though. This is puzzling me, some meshes make PV to crash, and 
>> others just show the bug you mentiones :-/
>> 
>> C.
>> 
>> 2018-03-26 21:07 GMT+02:00 Joachim Pouderoux <[email protected]>:
>>> Carlos,
>>> 
>>> For information, here is the merge request that address the wedge issue: 
>>>   https://gitlab.kitware.com/vtk/vtk/merge_requests/4059
>>> This is a simple patch for now, better solution will come.
>>> 
>>> Joachim
>>> 
>>> Joachim Pouderoux, PhD
>>> Technical Expert - Scientific Computing Team
>>> Kitware SAS
>>> 
>>> 2018-03-26 15:04 GMT-04:00 Carlos E Manglano-Villamarin 
>>> <[email protected]>:
>>>> Thanks Joachim,
>>>> 
>>>> I'll give it a go!
>>>> 
>>>> C.
>>>> 
>>>> 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux 
>>>> <[email protected]>:
>>>>> Carlos,
>>>>> 
>>>>> OpenFOAM can produce cells with non planar faces which is not handled by 
>>>>> VTK/ParaView. Moreover it appears that current reader implementation can
>>>>> also produce incorrect cells when reading wedge cells.
>>>>> Thanks to a recent rewriting of the polydron clipping algorithm, the 
>>>>> clipping/slicing of polyhedron should no more lead to crashes. 
>>>>> However,the problems
>>>>> of non planar faces might produce some holes in the result.
>>>>> We are currently working on a patch to better handle this case in the 
>>>>> reader.
>>>>> If you want to try the new polyhedron  clipping algorithm, you will have 
>>>>> to use ParaView >= 5.5 RC1.
>>>>> 
>>>>> Best regards,
>>>>> Joachim
>>>>> 
>>>>> 
>>>>> Joachim Pouderoux, PhD
>>>>> Technical Expert - Scientific Computing Team
>>>>> Kitware SAS
>>>>> 
>>>>> 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin 
>>>>> <[email protected]>:
>>>>>> 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 <[email protected]>:
>>>>>>> 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 
>>>>>>>> <[email protected]> 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
>>>>>>>> 
>>>>>>>> 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
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Powered by 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
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 
_______________________________________________
Powered by 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

Reply via email to