Memory leak
asl97 opened this issue · 0 comments
asl97 commented
everything was fine until i imported a image and added it into the node
more info from alleyoop, frontend of valgrind, killed quite early so it was just a little bit over 300mb
==30484== 304,576,976 bytes in 335 blocks are still reachable in loss record 1,076 of 1,076
==30484== at 0x04c2a77c: operator
==30484== by 0x0515c562: irr::video::CImage::initData() (in /usr/lib64/libIrrlicht.so.1.8.1)
==30484== by 0x0515c625: irr::video::CImage::CImage(irr::video::ECOLOR_FORMAT, irr::core::dimension2d<unsigned int> const&) (in /usr/lib64/libIrrlicht.so.1.8.1)
==30484== by 0x0512d54e: irr::video::CNullDriver::createImage(irr::video::ECOLOR_FORMAT, irr::core::dimension2d<unsigned int> const&) (in /usr/lib64/libIrrlicht.so.1.8.1)
==30484==
i notice there is a high cpu load when the texture menu is open once a image is loaded and selected (apply), might be link to the memory leak cause it only grow when the texture menu is open