René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"memory leaks on windows when using tinyobj_loader_opt.h","articleBody":"**Describe the issue**\r\n\r\nAfter calling \"parseObj\", lfpAlloc appears to leak memory. This seems to occur when vectors using lfpAlloc are resized, especially during emplace / push_back. This memory leak can be significantly large when loading hundreds of OBJ files.\r\n\r\nBy simply removing the \"lfpAlloc\" from all std::vectors used in tinyobj_loader_opt.h, I no longer leak memory.\r\n\r\n**To Reproduce**\r\n1. repeatedly call parseObj. \r\n2. profile memory usage\r\n3. observe a collection of \"lfpAlloc::Node\u003clfpAlloc::Chunk\u003c\u003c\u003e\u003e\"'s that should be free'd once parseOBJ returns, but are not.\r\n\r\nPlease attach minimal and reproducible files(source codes, .obj/.mtl files, etc)\r\n\r\nSee @ogrex 's comment on issue #153. Repro can be done by modifying the \"viewer.cc\" file to repeatedly load a moderately large obj file.\r\n\r\n**Expected behavior**\r\nOn return, parseOBJ should free all existing allocations to \"lfpAlloc::Node\u003clfpAlloc::Chunk\u003c\u003c\u003e\u003e\".\r\nAlternatively, lfpAlloc should be removed as a dependency of tinyobj_loader_opt.h entirely, as this seems to fix the memory leak. I do not notice a significant impact on performance by removing lfpAlloc, however, more testing might be required to validate this is true.\r\n\r\n**Environment**\r\n - TinyObjLoader version: tinyobj_loader_opt.h on d2cb6d2e3466af4cbcd139816a973ba749910025\r\n - OS: Windows 10\r\n - Compiler:  MSVC\r\n","author":{"url":"https://github.com/natevm","@type":"Person","name":"natevm"},"datePublished":"2020-10-10T05:12:35.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/283/tinyobjloader/issues/283"}