Mir

  1. Bug #1602199
  2. Comment #5

Comment 5 for bug 1602199

Revision history for this message
Kevin DuBois (kdub) wrote : Re: [testsfail] Process.*

iirc, Process* depends on the success of previous forks() (a bug in and of itself), but is not the root cause.

The cause seems to be a new libhybris release, which introduced a leak in the hw_get_module function. This function is used in platform probing, so it generates an error in valgrind.

unfortunately, valgrind seems to get confused about where this leak happens:
==8558==
==8558== 192 bytes in 1 blocks are definitely lost in loss record 246 of 271
==8558== at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8558== by 0xB56CE27: doc src
==8558== by 0xB56CFFB: doc src
==8558== by 0xB56C677: doc src
==8558== by 0xB77F59A: doc src
==8558== by 0xB77F97C: doc src
==8558== by 0xB77FC5E: doc src
==8558== by 0xB3697A8: doc src
==8558== by 0xAEB9030: std::_Tuple_impl<1ul, mir::ModuleDeleter<mir::test::doubles::NullPlatformIpcOperations> >::~_Tuple_impl() (tuple:339)
==8558== by 0x70469F: mir::graphics::module_for_device(std::vector<std::shared_ptr<mir::SharedLibrary>, std::allocator<std::shared_ptr<mir::SharedLibrary> > > const&, mir::options::ProgramOption const&) (platform_probe.cpp:38)

so I havent been able to come up with a suppression about it yet (which is the real fix)