"Didn't find pointer" message whist using multiprocessing

Hello,

I am having an issue whilst using NGSolve version 6.2.1908 in parallel on a Linux machine. The same code works on a Linux machine running NGSolve version 6.2.1905-45-g73eb677a and works for mac using 6.2.1905.

part of the message received was


Loading a nullptr
Typeids are different: ngfem::CoefficientFunction vs ngfem::ConstantCoefficientFunction
Reading pointer of type std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
Didn't find pointer, create new registry entry at 0Loading a nullptr

Store a possibly more complicated pointer
Reading pointer of type std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
Writeout version needed = Loading a nullptr

Reading pointer of type std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >Pickling output for object of type ngfem::CoefficientFunction = ([b'\xfd\xff\xff\xff"\x00\x00\x00ngfem::ConstantCoefficientFunction\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xf0?', b'\x00\x00\x00\x00\x00\x00\x00\x00', b'\x00\x00\x00\x00\x00\x00\x00\x00'],)


As far as I can tell the results obtained are still the same but there is a significant decrease in performance.

Kind regards,

Ben

Yes we added a lot more debug output while pickling... This is way too much for normal program run. As a workaround you can set the ngsglobals.msg_level down, we will reduce the default logging output from debug to info in future releases.

Thanks for reporting,
Best
Christopher

Hi Christopher,

That's excellent, thank you for your help.

Kind regards,

Ben