Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bull
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OptimalBits
  • bull
  • Issues
  • #806
Closed
Open
Issue created Dec 01, 2017 by Administrator@rootContributor

Timers not always being cleared when closing, causes hanging process

Created by: jeffijoe

I'm run into a weird issue with closing the queue.

When calling queue.close(), it seems the timeout created by https://github.com/OptimalBits/bull/blob/master/lib/queue.js#L803 is not cleared (even though I can see in the code that it should be). I found this using wtfnode as my Jest process would not exit.

Commenting out line 803 that creates the timer makes it work as expected.

Additionally, doing

queue.close().then(() => queue._clearTimers())

also fixes the issue. Perhaps running it again at the end of close might be a good idea?

Assignee
Assign to
Time tracking