Bug 1521447 Comment 14 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I was wrong that this happens during startup of Firefox. Nothing in the new logs shows output for that. Actually it's really all inside the cleanup steps of mozprocess. In all the working cases the `cleanup job io port` line can be seen three times after the `after cleanup` line. That has to come from `__del__`. In the failing case it is getting output only twice.

To know which of those invocations is missing I pushed one more try build:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=9292a361d4b13954b0a435f361f02a76ab0a6e02
I was wrong that this happens during startup of Firefox. Nothing in the new logs shows output for that. Actually it's really all inside the cleanup steps of mozprocess. In all the working cases the `cleanup job io port` line can be seen three times after the `after cleanup` line. That has to come from `__del__`. In the failing case it is getting output only twice.

To know which of those invocations is missing I pushed one more try build:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=19e412c6c8ff6a8647c659d657fc9908196477aa
I was wrong that this happens during startup of Firefox. Nothing in the new logs shows output for that. Actually it's really all inside the cleanup steps of mozprocess. In all the working cases the `cleanup job io port` line can be seen three times after the `after cleanup` line. That has to come from `__del__`. In the failing case it is getting output only twice.

To know which of those invocations is missing I pushed one more try build:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=837104880c51288a7e2a8e82fc0c9867c411d460

Back to Bug 1521447 Comment 14