381368 - WAV file is written to the log file and dumped to console

Status: VERIFIED DUPLICATE of bug 340314

(Other Applications :: ChatZilla, defect)

Description

[Andrew Smith]

Two or three times in the past few months I got the message (can't remember exactly what it says) "can't write to file:///home/andrew/.chatzilla/andr
ew/logs/%23seneca.log"

I have logging enabled for that channel and it would log just fine up until I got the error message.

This is not a permissions or a disk space problem, because if I reenable logging and restart chatzilla it would continue to work normally.

If I reenable logging and don't restart chatzilla logging is disabled as soon as there is something to write to the log.

While trying to figure out why this happens I noticed that there is some junk at the end of the log file. A visual inspection suggests this junk is exactly the beep.wav I use to beep at me. I will attach the config file so you know exactly when it's supposed to be used.

After talking to Gijs I enabled browser.dom.window.dump.enabled to see if that helps. Unfortunately it doesn't give any useful info but one interesting thing is that same wav file (I will attach it for reference) is dumped to the console sometimes. I belive that if it does happen it happens when I start chatzilla, but I see it so rarely I can'tbe sure.

I will also attach the dump output from one of the chatzilla sessions.

Unfortunately i cannot reproduce this but I'm filing the bug because it's potentially very serious and I'm hoping that if more people share their experiences with this issue a likely cause, or a way to reproduce will be identified.

These days I run, but the first time it happened I may have had earlier versions of either: Chatzilla 0.9.77-rdmsoft [XULRunner 1.8.0.4/2006060814]

Comment 1

[Andrew Smith]

Attachment: the log file created by chatzilla

this is only part of the log file, i cut most of it out so that bugzilla won't complain. the junk is at the bottom.

Comment 2

[Andrew Smith]

Attachment: the beep.wav that ends up in strange places

Comment 3

[Andrew Smith]

Attachment: my prefs.js

Comment 4

[Andrew Smith]

Attachment: copy-paste of the console dump

Comment 5

[James Ross]

Could I get you to confirm that you are experiencing this problem on Linux? (The sound playing code in Mozilla is unique to each platform.)

This looks on initial inspection like Mozilla is crapping over its file descriptors and re-using open ones or similar. Quite impressive. :)

Comment 6

[Andrew Smith]

yes, it's a 32-bit slackware.

Comment 7

[:Gavin Sharp [email: [e-mail]]]

Reminds me of bug 340314, which was fixed for 1.8.1. Sounds like you're using a 1.8.0 Xulrunner build?

Comment 8

[:Gavin Sharp [email: [e-mail]]]

Oh, and also fixed for 1.8.0.7, which is newer than your XULRunner 1.8.0.4. You should upgrade :)