Some packages (like orchestra/testbench) may symlink the vendor folder, causing an infinitly nested folder structure, leaving CodeLite stuck trying to analyze the files and eventually consuming all memory.
I'm not 100% sure but I think this happens somewhere in the parser since it appears to finish the "scanning for workspace files" step before getting stuck, though the file list never appears in the workspace panel.
What happened?
Some packages (like
orchestra/testbench) may symlink the vendor folder, causing an infinitly nested folder structure, leaving CodeLite stuck trying to analyze the files and eventually consuming all memory.I'm not 100% sure but I think this happens somewhere in the parser since it appears to finish the "scanning for workspace files" step before getting stuck, though the file list never appears in the workspace panel.
Version
Other
Operating system
Linux
Steps to reproduce
No response
Relevant log output