My reliable repro was actually a much less intensive `watch 'pstree -aup' | grep "..."`
With the default watch interval of 2 seconds, I would reliably hit this 1-2 times per day with it running continuously in the background. Process churn isn't crazy, but I am regularly compiling various things. I actually debugged the issue to make sure it was consistent and not RAM failing (this is in a desktop with non-ECC RAM). I hate to say it's not critical at the risk of this ticket being closed WONT_FIX but it is not actually a critical issue. Would be nice to have fixed, even if it is just an if()-guard added to the existing version. How involved is that process? Is it something I could submit a patch for? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755681 Title: pstree crashes on fclose(NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1755681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
