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

one setInterval() is causing node running forever. #90

Open
Cojad opened this issue Dec 14, 2022 · 1 comment
Open

one setInterval() is causing node running forever. #90

Cojad opened this issue Dec 14, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@Cojad
Copy link

Cojad commented Dec 14, 2022

setInterval(() => {

I used tool "why-is-node-running" to figure out why my code won't exit after almost an hour.

I think this code maybe is for statsical need on signServer. But using this way to track tiktok id usage will result node running forever even there is no other event need node to run.

Maybe you can try add timestamp to each uu element then do the check for 30mins old uu every time before sending uu to signServer. So you don't need to check in setInternal.

@zerodytrash
Copy link
Owner

True. That should be changed.

@zerodytrash zerodytrash added the enhancement New feature or request label Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants