Paraview quit unexpectedly when opening exodus file

Hi,

I’m trying to open an exodus file on a Mac M1 using v.10, both arm64 and x86, but Paraview crashes immediately. I’ve tried some the suggestions in this thread (ParaView on new Macs with M1 chips?) but with no success. Thanks in advance.

please share your data

Hi Mathieu,

Thank you for the assistance, I’m attaching the file itself as well as the crash report I got. I should mention that I can open this file fine on an older Intel Mac with Paraview 5.9.0
Problem_report_paraview.txt (137.1 KB)

.i file are not Exodus files afaik.

I didn’t notice I sent the wrong file, sorry about that. Here is the Exodus file.
ion_E_test_6_out_01.e (1.1 MB)

I confirm that there is segfault with the new IOSS reader.

Thread 1 "paraview" received signal SIGABRT, Aborted.
0x00007ffff7e10d22 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007ffff7e10d22 in raise () from /usr/lib/libc.so.6
#1  0x00007ffff7dfa862 in abort () from /usr/lib/libc.so.6
#2  0x00007ffff7dfa747 in __assert_fail_base.cold () from /usr/lib/libc.so.6
#3  0x00007ffff7e09616 in __assert_fail () from /usr/lib/libc.so.6
#4  0x00007fffdb7da519 in vtkioss_Ioex::DatabaseIO::get_sidesets (this=0x55555b567f70) at /home/glow/work/paraview/pv1/src/VTK/ThirdParty/ioss/vtkioss/exodus/Ioex_DatabaseIO.C:1682
#5  0x00007fffdb7d1757 in vtkioss_Ioex::DatabaseIO::read_meta_data__ (this=0x55555b567f70) at /home/glow/work/paraview/pv1/src/VTK/ThirdParty/ioss/vtkioss/exodus/Ioex_DatabaseIO.C:507
#6  0x00007fffdb6e52fd in vtkioss_Ioss::DatabaseIO::read_meta_data (this=0x55555b567f70) at /home/glow/work/paraview/pv1/src/VTK/ThirdParty/ioss/vtkioss/Ioss_DatabaseIO.h:321
#7  0x00007fffdb6c7ec6 in vtkioss_Ioss::Region::Region (this=0x555559afcf10, iodatabase=0x55555b567f70, my_name="") at /home/glow/work/paraview/pv1/src/VTK/ThirdParty/ioss/vtkioss/Ioss_Region.C:316
#8  0x00007fffe8e9edeb in __gnu_cxx::new_allocator<vtkioss_Ioss::Region>::construct<vtkioss_Ioss::Region, vtkioss_Ioss::DatabaseIO*> (this=0x7fffffffc16f, __p=0x555559afcf10) at /usr/include/c++/11.1.0/ext/new_allocator.h:156
#9  0x00007fffe8e9d784 in std::allocator_traits<std::allocator<vtkioss_Ioss::Region> >::construct<vtkioss_Ioss::Region, vtkioss_Ioss::DatabaseIO*> (__a=..., __p=0x555559afcf10) at /usr/include/c++/11.1.0/bits/alloc_traits.h:512
#10 0x00007fffe8e9c06e in std::_Sp_counted_ptr_inplace<vtkioss_Ioss::Region, std::allocator<vtkioss_Ioss::Region>, (__gnu_cxx::_Lock_policy)2>::_Sp_counted_ptr_inplace<vtkioss_Ioss::DatabaseIO*> (this=0x555559afcf00, __a=...)
    at /usr/include/c++/11.1.0/bits/shared_ptr_base.h:519
#11 0x00007fffe8e996ee in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::__shared_count<vtkioss_Ioss::Region, std::allocator<vtkioss_Ioss::Region>, vtkioss_Ioss::DatabaseIO*> (this=0x7fffffffc318, __p=@0x7fffffffc310: 0x0, 
    __a=...) at /usr/include/c++/11.1.0/bits/shared_ptr_base.h:650
#12 0x00007fffe8e962a4 in std::__shared_ptr<vtkioss_Ioss::Region, (__gnu_cxx::_Lock_policy)2>::__shared_ptr<std::allocator<vtkioss_Ioss::Region>, vtkioss_Ioss::DatabaseIO*> (this=0x7fffffffc310, __tag=...)
    at /usr/include/c++/11.1.0/bits/shared_ptr_base.h:1337
#13 0x00007fffe8e8ff93 in std::shared_ptr<vtkioss_Ioss::Region>::shared_ptr<std::allocator<vtkioss_Ioss::Region>, vtkioss_Ioss::DatabaseIO*> (this=0x7fffffffc310, __tag=...) at /usr/include/c++/11.1.0/bits/shared_ptr.h:409
#14 0x00007fffe8e8558b in std::allocate_shared<vtkioss_Ioss::Region, std::allocator<vtkioss_Ioss::Region>, vtkioss_Ioss::DatabaseIO*> (__a=...) at /usr/include/c++/11.1.0/bits/shared_ptr.h:861
#15 0x00007fffe8e7bd6d in std::make_shared<vtkioss_Ioss::Region, vtkioss_Ioss::DatabaseIO*> () at /usr/include/c++/11.1.0/bits/shared_ptr.h:877
#16 0x00007fffe8e5f9a9 in vtkIOSSReader::vtkInternals::GetRegion (this=0x55555b9f6020, dbasename="/home/glow/tmp/ion_E_test_6_out_01.e", fileid=0) at /home/glow/work/paraview/pv1/src/VTK/IO/IOSS/vtkIOSSReader.cxx:1418
#17 0x00007fffe8e5ca25 in vtkIOSSReader::vtkInternals::UpdateTimeInformation (this=0x55555b9f6020, self=0x7fffd4008500) at /home/glow/work/paraview/pv1/src/VTK/IO/IOSS/vtkIOSSReader.cxx:951
#18 0x00007fffe8e69e0d in vtkIOSSReader::ReadMetaData (this=0x7fffd4008500, metadata=0x55555b9f3ce0) at /home/glow/work/paraview/pv1/src/VTK/IO/IOSS/vtkIOSSReader.cxx:2974
#19 0x00007ffff261fde5 in vtkReaderAlgorithm::ProcessRequest (this=0x7fffd4008500, request=0x55555b562a60, outInfo=0x55555b9c4b60) at /home/glow/work/paraview/pv1/src/VTK/Common/ExecutionModel/vtkReaderAlgorithm.cxx:78
#20 0x00007fffe8e6b416 in vtkIOSSReader::ProcessRequest (this=0x7fffd4008500, request=0x55555b562a60, inInfo=0x0, outInfo=0x55555b9c4b60) at /home/glow/work/paraview/pv1/src/VTK/IO/IOSS/vtkIOSSReader.cxx:3258
#21 0x00007ffff25f6679 in vtkExecutive::CallAlgorithm (this=0x55555b68ba40, request=0x55555b562a60, direction=1, inInfo=0x0, outInfo=0x55555b9c4b60) at /home/glow/work/paraview/pv1/src/VTK/Common/ExecutionModel/vtkExecutive.cxx:734
#22 0x00007ffff25ee161 in vtkDemandDrivenPipeline::ExecuteInformation (this=0x55555b68ba40, request=0x55555b562a60, inInfoVec=0x0, outInfoVec=0x55555b9c4b60)

@ASKapat please open a issue on our gitlab: https://gitlab.kitware.com/paraview/paraview/-/issues and use ParaView 5.9.1 for the time being.

FYI @utkarsh.ayachit

It’s failing on this assertion:

paraview: /home/utkarsh/Kitware/ParaView3/ParaView/VTK/ThirdParty/ioss/vtkioss/exodus/Ioex_DatabaseIO.C:1682: void vtkioss_Ioex::DatabaseIO::get_sidesets(): Assertion `side_topo != 
nullptr' failed.               

I suspect the side-sets are not described correctly. Running tools like io_info provided by IOSS also fail on this file. How was this file written out? If you’re assured it’s a valid file, feel free to raise an issue with IOSS here. In the meantime, you can use the LegacyExodusIIReader plugin and the Legacy Exodus reader to read the file.

I had no idea, thanks @utkarsh.ayachit

@mwestphal @utkarsh.ayachit

I’m now able to open the exodus files using the LegacyExodusIIReader plugin, thank you for the feedback and guidance!

Hi I had a very similar issue. Is there a way to make it such that executing

$ paraview file.e &

always uses the legacy exodus reader without having to make that selection every time I open paraview? I know that I can set the legacy exodus reader as the default in a given paraview session. But I haven’t come across a way to make it a permanent default

WHen you set it as default, it is save in your settings and should be used everytime after that.