Re: [Vala] FileStream not closed after going out of scope

2012-09-25 Thread tomw
But the real problem is that you don't really close the input and error file descriptors and according to the docs [1] you should or if you aren't interested in the input / error fds you can pass null to the function. Thanks for all the input. Not closing the input/error fds was the issue.

Re: [Vala] FileStream not closed after going out of scope

2012-09-25 Thread Andrea Del Signore
On Tue, Sep 25, 2012 at 11:32 AM, tomw t...@ubilix.com wrote: But the real problem is that you don't really close the input and error file descriptors and according to the docs [1] you should or if you aren't interested in the input / error fds you can pass null to the function. Thanks for

Re: [Vala] FileStream not closed after going out of scope

2012-09-24 Thread tomw
ok, here's a bit more meat. Hopefully this help to tackle the issue: currently I'm using Vala 0.17.6. Obviously some files are left open as the open file count is increasing (checking with lsof | wc -l ) until I get the span error: Error spawning Uptime process - Failed to create pipe for

Re: [Vala] FileStream not closed after going out of scope

2012-09-24 Thread mar...@saepia.net
try something like this (it is only a demonstration, not working code!) key to solve problem you've encountered are io_stdout = null; io_stderr = null; it unrefs io channel, and releases descriptors private IOChannel io_stderr; private IOChannel

Re: [Vala] FileStream not closed after going out of scope

2012-09-24 Thread Nor Jaidi Tuah
bool res = Process.spawn_async_with_pipes (null, runme, null,

[Vala] FileStream not closed after going out of scope

2012-09-19 Thread tomw
Hi, spawning a process and reading the returned pipe in a method like: ... int input; int output; int error; Pid child_pid; bool res = Process.spawn_async_with_pipes (null, runme,