Skip to content

Unclosed file handles #7

@saurako

Description

@saurako

Hi,
I've been using this module for a project I'm working on and it is a great fit for my needs. Really appreciate the work here.
Over the course of a month of running a process that uses the BigQueue though, I've found that it leaves behind a trail of unclosed file handles. Here's an example:

$ sudo lsof -n | grep -i "DEL"
node       4291       	  saurako  DEL       REG              202,1               394612 /home/saurako/data-processor/data/page-66.dat
node       4291       	  saurako  DEL       REG              202,1               394610 /home/saurako/data-processor/data/page-64.dat
node       4291       	  saurako  DEL       REG              202,1               394611 /home/saurako/data-processor/data/page-65.dat
node       4291       	  saurako  DEL       REG              202,1               394557 /home/saurako/data-processor/data/page-62.dat
node       4291       	  saurako  DEL       REG              202,1               394555 /home/saurako/data-processor/data/page-61.dat
node       4291       	  saurako  DEL       REG              202,1               394558 /home/saurako/data-processor/data/page-63.dat
node       4291       	  saurako  DEL       REG              202,1               394554 /home/saurako/data-processor/data/page-60.dat
node       4291       	  saurako  DEL       REG              202,1               394552 /home/saurako/data-processor/data/page-58.dat

Can you guys please help in fixing this? I'm using the BigQueue data structure, and simply enqueue and dequeue messages from the queue. I do not explicitly close anything, but should I be doing that? If yes, then I'm not sure what should signal that I need to do that?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions