OK - this is a strange one, but with some effort I've been able to replicate it. It looks like when two packages both have a dependency on fstream and those two packages are then included in a project, you end up with call stack exceeded errors.

I found this when building http://github.com/steelmesh/attachmate which has been made to work with the fstream module, and I think it works pretty well.

Unfortunately when I got to using both attachmate and tar in a project, I started seeing call stack errors :(

I've created a test project @ https://github.com/DamonOehlman/fstream-callstack-test which replicates the issue, and to be honest I'm not sure if this is an fstream issue or a node issue... sorry. I've generated a module debug log at https://github.com/DamonOehlman/fstream-callstack-test/blob/master/module-debug.log which might shed some light on things too.

Anything else I can do, then please let me know. Dead keen to make use of fstream for other things :)

Cheers,
Damon.