Mzack9999

This is for sure an interesting feature, but I'm not sure it can be fully applied to the crawling process. While it's easy to mimic it avoiding overwriting existing files,...

Please fill all the fields within the [new issue template](https://github.com/projectdiscovery/katana/issues/new?assignees=&labels=Type%3A+Bug&projects=&template=issue-report.md) otherwise it's impossible for us to investigate something we are unable to reproduce. I see you have also `httpx` running,...

Related https://github.com/projectdiscovery/katana/issues/579

@DeC1pher, would it be possible to provide the output of the `go env` command? I tried to exclude the faulty architecture, but it seems like it's not `armv7l`: ```go //go:build...

I'm unable to reproduce it. I just tried on a fresh install of the latest Kali Linux: ```console $ sudo apt install golang $ go env ... GOARCH="amd64" GOVERSION="go1.19.4" $...

@abhijithpa Thanks for confirming - I'm closing the issue as complete

I don't think this is a bug but rather the standard behaviour of browsers. The code visible within the browser preview of the DOM is a fake version of the...

Potentially related too https://github.com/projectdiscovery/nuclei/issues/5165

@AlexS778 After investigating it seems like this is related to https://github.com/projectdiscovery/nuclei/issues/5165 - The issue is yet another internal memory reference preventing gc from recycling objects (similarly to https://github.com/projectdiscovery/nuclei/issues/4836). In this...

@AlexS778 When using nuclei as SDK, probably with V3 introduction or the more recent https://github.com/projectdiscovery/nuclei/pull/5112, when invoking `NucleiEngine.Close(...)` the internal global instances of levelDB (used for various shared tasks) are...