| Subject: | Devel::NYTProf support |
It's come up a few times but I don't think we ever got around to raising as an RT:
Devel::NYTProf uses a filehandle to write profiling events, so it gets confused when IO::Async::Process closes the filehandles before a fork. This shows up as corrupted files and warnings from code using Devel::NYTProf.
Workarounds include starting the profiler just before the first entry into the event loop, after the resolver and any other forking code has been set up. Turning off NYTProf compression can help as well (not practical for larger applications, unfortunately).
Not sure if nytprof itself has any hooks to identify which filehandles it's using, will update ticket if I have any more info.
cheers,
Tom