Skip to content

Conqueterm instances are not closed, leaving zombie ruby process #25

@skwp

Description

@skwp

When you close a buffer running a (completed) conque, the ruby process hangs around, eating up a tty (causing 'unable to fork' errors in iterm), and other problems. Need to figure out how to nuke the ruby process once it's finished running. This is not a problem when you run a regular rspec command yet conque makes it hang around for some reason.

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