671801 - Mac OSX: Log file not updating after sleep/rewake and sometimes randomly after some time

Status: RESOLVED WONTFIX

(NSPR :: NSPR, defect)

Description

[Vitus LM]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0.1) Gecko/20100101 Firefox/5.0.1
Build ID: 20110707182747

Steps to reproduce:

I have NSPR_LOG_FILE and LOG_MODULES set and logging everything to a file. When I open TB5 it logs like it should.
Now I close the lid of my MBP, put it sleep and wake it up again after a few minutes, without quitting TB.
Switch to TB and tell it to check the mail.

Sometimes this also happens randomly after TB has been running and sitting in the bg for a while, which I like to do. It's set to check the mail every 10m so I now if there's  new mail. When doing that, sometimes I noticed the same behavior: TB still checks the mail, sends mail etc, but TBT does not show anything.


Actual results:

TB5 checks the mail, as reflected in the statusbar at the bottom, but the logfile does not show any of this. It only shows DNS reqs made simultaneously by FF, because it picks up on the nsHostResolver:4 which is globally defined.
That means that it works in FF.


Expected results:

It should continue updating the logfile like before putting it to sleep.
AFAIR that was the case in TB4 and before.
This is a problem because it causes TBTracer (which I am the developer of) to not update anymore. At first, I was suspecting a bug in TBT, but then found out that the logfile is to blame.

Comment 1

[Vitus LM]

Some additional info:
It seems that it is not a problem of the sleep/wake cycle, but the fact that both FF and TB log to the same file. If I remove nsHostResolver, or FF is not running it is not a problem.
From what I've seen so far, it seems to work if I start TB first, and then FF, both logs appear in the file.
If, on the other hand, I first start FF and then TB, TB logs when it starts up, but stops as soon as FF adds something to the file.

At this point I am not sure if this should be considered a bug or just a quirky side-effect of having multiple NSPR progs use the same logfile.
Does anyone know or care to discuss what the official stance on this should be?

Comment 2

[Wan-Teh Chang]

Vitus: thank you for the bug report.  Right now multiple processes cannot
use the same log file.  There is a bug report to eliminate this limitation.
There are cases where people want multiple processes to log to the same
file so that the events from multiple processes can interleave properly in
chronological order.

In your case, I guess you don't need FF and TB to log to the same file, so
the best workaround is to have them log to different files.