Paraview launching error after setting autompi option

ParaView Support
1

Dear Friends,
In the settings panel, i have enabled Auto MPI option and relaunched paraview. But got following error and paraview GUI does not appear. The screen trace is as follows:

AutoMPI: SUCCESS: command is:
"/home/vinod/Downloads/PARAview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/mpiexec" "-n" "2" "/home/vinod/Downloads/PARAview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/pvserver" "--server-port=43423"
AutoMPI: starting process server
-------------- server output --------------
Waiting for client...
AutoMPI: server successfully started.
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc

Loguru caught a signal: SIGABRT
Stack trace:
57 0x407b2a /home/vinod/Downloads/PARAview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/paraview-real() [0x407b2a]
56 0x7fdbdee0009b __libc_start_main + 235
55 0x40776d /home/vinod/Downloads/PARAview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/paraview-real() [0x40776d]
54 0x40c6d0 /home/vinod/Downloads/PARAview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/paraview-real() [0x40c6d0]
53 0x408978 /home/vinod/Downloads/PARAview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/paraview-real() [0x408978]
52 0x7fdbdea88a19 pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) + 1049
51 0x7fdbde9fb366 pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior(QObject*) + 310
50 0x7fdbde9fb1ee pqAlwaysConnectedBehavior::serverCheck() + 174
49 0x7fdbdd3f575d pqObjectBuilder::createServer(pqServerResource const&, int) + 605
48 0x7fdbdb66a256 vtkSMSession::ConnectToSelf(int) + 70
47 0x7fdbdb669520 vtkSMSession::ConnectToRemoteInternal(char const*, int, bool, int) + 1040
46 0x7fdbda886388 vtkProcessModule::RegisterSession(vtkSession*) + 376
45 0x7fdbd5ba2102 /home/vinod/Downloads/PARAview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/libvtkCommonCore-pv5.9.so.1(+0x3f3102) [0x7fdbd5ba2102]
44 0x7fdbd5a29209 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 25
43 0x7fdbdbb72f10 /home/vinod/Downloads/PARAview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/libvtkGUISupportQt-pv5.9.so.1(+0x39f10) [0x7fdbdbb72f10]
42 0x7fdbdbb5f2ab /home/vinod/Downloads/PARAview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/libvtkGUISupportQt-pv5.9.so.1(+0x262ab) [0x7fdbdbb5f2ab]
41 0x7fdbdc2bf1ea QMetaObject::activate(QObject*, int, int, void**) + 1850
40 0x7fdbdd38b7b9 /home/vinod/Downloads/PARAview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/libpqCore-pv5.9.so.1(+0x7a7b9) [0x7fdbdd38b7b9]
39 0x7fdbdd3884f2 pqServerManagerObserver::connectionCreated(long long) + 50
38 0x7fdbdc2bf1ea QMetaObject::activate(QObject*, int, int, void**) + 1850
37 0x7fdbdd44240d pqServerManagerModel::onConnectionCreated(long long) + 637
36 0x7fdbdb619c68 vtkSMParaViewPipelineController::InitializeSession(vtkSMSession*) + 1544
35 0x7fdbd232d21c vtkSMMaterialLibraryProxy::Synchronize() + 604
34 0x7fdbdb6705bb vtkSMSessionClient::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 347
33 0x7fdbdb5612e5 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 53
32 0x7fdbdb5622bb vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 59
31 0x7fdbdb562482 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 242
30 0x7fdbda413ddd vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
29 0x7fdbda413b3e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1294
28 0x7fdbda41340d vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1229
27 0x7fdbda412da9 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
26 0x7fdbd312378e vtkPVMaterialLibraryCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 1886
25 0x7fdbd0eec6ed vtkOSPRayMaterialLibrary::InternalParse(char const*, bool) + 317
24 0x7fdbd0eeb1fe vtkOSPRayMaterialLibrary::InternalParseJSON(char const*, bool, std::istream*) + 110
23 0x7fdbd9f88726 vtkJson::parseFromStream(vtkJson::CharReader::Factory const&, std::istream&, vtkJson::Value*, std::string*) + 406
22 0x7fdbd9f8830c vtkJson::OurReader::parse(char const*, char const*, vtkJson::Value&, bool) + 428
21 0x7fdbd9f87c8b vtkJson::OurReader::readValue() + 251
20 0x7fdbd9f87710 vtkJson::OurReader::readObject(vtkJson::OurReader::Token&) + 528
19 0x7fdbd9f87c8b vtkJson::OurReader::readValue() + 251
18 0x7fdbd9f87710 vtkJson::OurReader::readObject(vtkJson::OurReader::Token&) + 528
17 0x7fdbd9f87c8b vtkJson::OurReader::readValue() + 251
16 0x7fdbd9f87710 vtkJson::OurReader::readObject(vtkJson::OurReader::Token&) + 528
15 0x7fdbd9f87c8b vtkJson::OurReader::readValue() + 251
14 0x7fdbd9f87710 vtkJson::OurReader::readObject(vtkJson::OurReader::Token&) + 528
13 0x7fdbd9f87dab vtkJson::OurReader::readValue() + 539
12 0x7fdbd9f7e7c1 vtkJson::OurReader::decodeString(vtkJson::OurReader::Token&) + 49
11 0x7fdbd9f7dfb4 vtkJson::OurReader::decodeString(vtkJson::OurReader::Token&, std::string&) + 52
10 0x7fdbd521bb94 std::string::reserve(unsigned long) + 52
9 0x7fdbd521baeb std::string::_Rep::_M_clone(std::allocator<char> const&, unsigned long) + 27
8 0x7fdbd521ac79 std::string::_Rep::_S_create(unsigned long, unsigned long const&) + 89
7 0x7fdbd51dd01c /lib/x86_64-linux-gnu/libstdc++.so.6(+0x9301c) [0x7fdbd51dd01c]
6 0x7fdbd51dcb34 /lib/x86_64-linux-gnu/libstdc++.so.6(+0x92b34) [0x7fdbd51dcb34]
5 0x7fdbd51dc901 /lib/x86_64-linux-gnu/libstdc++.so.6(+0x92901) [0x7fdbd51dc901]
4 0x7fdbd51dc8c6 /lib/x86_64-linux-gnu/libstdc++.so.6(+0x928c6) [0x7fdbd51dc8c6]
3 0x7fdbd51d6983 /lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c983) [0x7fdbd51d6983]
2 0x7fdbdedfe535 abort + 289
1 0x7fdbdee137bb gsignal + 267
0 0x7fdbdee13840 /lib/x86_64-linux-gnu/libc.so.6(+0x37840) [0x7fdbdee13840]
( 14.467s) [paraview ] :0 FATL| Signal: SIGABRT
error: exception occurred: Child aborted

How do I handle this issue?
Thanks in advance
Vinod

2

this error usually indicates that memory allocation failed. You should check your computer memory usage. Maybe your dataset is too big for the available RAM?

3

First, let me say that this is very likely not an “out of memory” error, as this is occurring in startup. Next, I would VERY STRONGLY suggest not turning on Auto MPI. There is a reason it is on the advanced panel. This feature has also been removed in ParaView 5.10.0, as MPI and multi-threading (which is more and more being used by ParaView filters) appear to clash.

Now that you are crashing on startup, the way to recover is to delete all the files in ~/.config/ParaView. Then, try running ParaView again.
Alan

1 Like
4

Dear Mazen and Walter,
I started working on paraview 5.10.0 now and still at launch time it was crashing.
So I had a detailed look into the memory usages during paraview launch and during processing.
To My surprise, it came out to be a RAM issue. I found that My system RAM was loaded with other applications as well. So when I closed everything and used paraview it worked fine (probably this particular case was heavy).

Now coming to one more observation of crashing at launch time itself. I was launching paraview immediately after the crash. So when I monitored in top , I found that after crash , paraview is still active and the RAM is getting released slowly. It took almost half a minute for paraview process to completely get cleaned up from top. So when I immediately launch paraview it again crashes, because just paraview launch itself is consuming ~1.5GB.

Thanks for the suggestion and prompt replies.
Vinod