Ticket #181 (new Bug)

Opened 6 years ago

doesn't manage ispell pipes correctly - will hang if ispell exits

Reported by: cg2v Owned by: Cyrus Daboo
Priority: major Milestone: unassigned
Component: Application Version: v4.0.7
Severity: Crash/data loss Keywords:
Cc: Operating System: Linux
OS Version:

Description

mulberry does not close pipe endpoints that it is not using. For instance, all four filedescriptors for the mulberry/ispell pipe are left open in the parent process:

mulberry4 3319 cg2v 9r FIFO 0,5 2009162 pipe mulberry4 3319 cg2v 10w FIFO 0,5 2009162 pipe mulberry4 3319 cg2v 11r FIFO 0,5 2009163 pipe mulberry4 3319 cg2v 12w FIFO 0,5 2009163 pipe

This means that if ispell does not start up correctly or is killed for some reason, mulberry will end up deadlocking on it (trying to read from fd 11, when nothing will ever appear there again)

Note: See TracTickets for help on using tickets.