Using 040915 builds, www.netscape.com does not seem to load on Linux. Works on latest Mac and Windows builds. It doesn't crash or lock up or anything, just nothing lays out. Not even sure if all the html gets downloaded. Not sure who to assign this to, since I can't tell what the problem is. Rick?

Marking for M4 consideration and setting self as QA contact (and changing OS to Linux)

ramiro/chris, can you check your latest builds and see if you can reproduce?

this is one of the tests we execute before we release to qa. i just verified it again, and www.netscape.com loads and renders fine.

Upon further review, it is getting hung reading my cookies file, which looks very ugly for some reason. Changing assigned to morse, and attaching the cookies file. Since no one else seems to be seeing this, will mark M5 unless morse decides it's something bad.

Okay got it. Every time you set a cookie, then exit, it appends the entire cookies file to the already existing cookies file, so you have a rapidly mutating file. Eventually, it must get too large. This could mess up Linux users. Will set back to M4 (sorry) for consideration.

Hmm, this smells very familiar. Judson made a change last fall in the way files are written out. In particular, he changed the definition of NET_XP_FileOpen which is the routine used to create/update the cookie file. As a result of this change, cookie files were no longer being created on windows if they didn't already exist. I found the problem and fixed it. See bug report 2414. The fix was very platform-dependent. It had to do with the mode in which the file was opened. The particular mode that was being used for windows was to overwrite an existing file but not create a file if it didn't already exist. After I closed out the bug report, paulmac reopened it saying it was still failing on mac. This is very believable because the mode for opening files differs on the different platforms. And the symptoms described in this bug report sound like exactly the same problem -- the cookie file on linux is probably being opened in some sort of "append" mode rather than in an "overwrite" mode. As of Judson's return, I had reassigned bug 2414 back to him since it was his code change that caused the problem in the first place. And I am marking this bug a duplicate of 2414 because I'm convinced both bugs are related to the file-open mode on the various platforms. *** This bug has been marked as a duplicate of 2414 ***

Moving all Apprunner bugs past and present to Other component temporarily whilst don and I set correct component. Apprunner component will be deleted/retired shortly.