From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22 i686; en-US; m18) Gecko/20001205 BuildID: 2000120508 The attached cookperm.txt does not populate the Image Manager. You can delete any single line and the Image Manager will be populated correctly. Reproducible: Always Steps to Reproduce: 1. Place this cookperm.txt in a new user directory that has image and cookie loading set to prompt. 2. Start Mozilla and open the Image Manager. Notice the window is empty. 3. Exit Mozilla and edit the file to remove a line (say the first, www.ground.com). 4. Start Mozilla and open the Image Manager. Notice the window is populated properly. Actual Results: The Image Manager window is empty, but Cookie Manager has content. (If cookies have actually been set, the Cookie List will also have content.) Expected Results: Both before and after removing lines, the Image Manager should show all of the sites. This is a very reduced version of my cookperm.txt. I haven't exhaustively tested removing each of the 230+ entries, but the 10 random ones I removed caused the behaviour described.
Assignee: mstoltz → morse
Component: Security: General → Cookies
QA Contact: ckritzer → tever
I see the problem. There's a hard-coded limit on the size of a buffer in nsCookie.cpp (search for BUFLEN2). I'm working on it and should have a fix by the end of the day.
*** Bug 58977 has been marked as a duplicate of this bug. ***
*** Bug 60567 has been marked as a duplicate of this bug. ***
*** Bug 62053 has been marked as a duplicate of this bug. ***
Created attachment 20527 [details] [diff] [review] Patch for nsCookie.cpp, wallet.cpp, singsign.cpp, & CookieViewer.js
Your description makes sense and the patch looks like it does what was described. If it tests out, r:pnunn. (sorry the r: took so long.) -p
sr=alecf thanks for cleaning this up
Fix checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
*** Bug 63622 has been marked as a duplicate of this bug. ***
*** Bug 64275 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.