So, as for 1) This is actually not going to be very useful - the problem sounds like the child processes are not starting, and those are sandboxed, so they cannot access the console. (You could still get some debug output from the parent, but not everything) 2) Those default settings log a lot of info about the network connections, but again I suspect that's probably not related to this failure, so I would ignore that for now (especially because that could have quite some private info). We may ask for another log with different later. The crash reports are hangs on shutdown, but they do show that ESET is *still* injecting into and modifying Firefox even if you disable it.
Bug 1769414 Comment 23 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
So, as for 1) This is actually not going to be very useful - the problem sounds like the child processes are not starting, and those are sandboxed, so they cannot access the console. (You could still get some debug output from the parent, but not everything) 2) Those default settings log a lot of info about the network connections, but again I suspect that's probably not related to this failure, so I would ignore that for now (especially because that could have quite some private info). We may ask for another log with different settings later. The crash reports are hangs on shutdown, but they do show that ESET is *still* injecting into and modifying Firefox even if you disable it.
So, as for 1) This is actually not going to be very useful - the problem sounds like the child processes are not starting, and those are sandboxed, so they cannot access the console. (You could still get some debug output from the parent, but not everything) 2) Those default settings log a lot of info about the network connections, but again I suspect that's probably not related to this failure, so I would ignore that for now (especially because that could have quite some private info). We may ask for another log with different settings later. The crash reports are hangs on shutdown, but they do show that ESET is *still injecting into and modifying Firefox even if you disable it*.