Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixed Multiple instances cache goroutine leaks #2373 #2386

Closed
wants to merge 5 commits into from
Closed

fixed Multiple instances cache goroutine leaks #2373 #2386

wants to merge 5 commits into from

Conversation

hktalent
Copy link
Contributor

@hktalent hktalent commented Aug 3, 2022

Proposed changes

Checklist

  • Pull request is created against the dev branch
  • All checks passed (lint, unit/integration/regression tests etc.) with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

x51pwn and others added 4 commits July 28, 2022 23:09
substr('xxtestxxx',2)。   testxxx
substr('xxtestxxx',2,-2)  testx
substr('xxtestxxx',2,6)   test

2、add DSL aes_cbc for #2243 By @hktalent
aes_cbc("key111key111key111key111", "dataxxxxxxdataxxxxxxdataxxxxxxdataxxxxxxdataxxxxxx")

3、fixed An error occurs when running nuclei with multiple instances #2301 By @hktalent
@hktalent
Copy link
Contributor Author

hktalent commented Aug 3, 2022

@ehsandeep
Local concurrent, multi-instance nuclei tests for several days to confirm that there is no cache leak

@hktalent
Copy link
Contributor Author

hktalent commented Aug 3, 2022

How to test for cache memory leaks?
Start debug mode

import (
"net/http"
_ "net/http/pprof"
)
go func() {
http.ListenAndServe(":6060", nil)
}()

After calling nuclei to scan,
run
go tool pprof -seconds=10 -http=:9999 http://localhost:6060/debug/pprof/heap
Open browser access;
http://127.0.0.1:6060/debug/pprof/goroutine?debug=2
You can see that the cache always exists

@ehsandeep ehsandeep changed the base branch from master to dev August 3, 2022 08:14
@ehsandeep
Copy link
Member

Closing as duplicate of #2390

@ehsandeep ehsandeep closed this Aug 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants