Closed
Bug 97422
Opened 24 years ago
Closed 17 years ago
Cache issues when network connection gets dropped.
Categories
(MailNews Core :: Networking: NNTP, defect)
MailNews Core
Networking: NNTP
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: stephend, Unassigned)
References
Details
Attachments
(3 files)
Build ID: 2001-08-28-03, Windows 2000.
Summary: Cache issues when network connection gets dropped.
Steps to Reproduce:
1. Connect to a newsserver (I used news://poisonivy.mcom.com) and subscribe to
a group.
2. Read a couple of postings, doesn't matter what you read.
3. Drop your connection to the network (if on dialup, disconnect, if on LAN,
pull RJ-45 cable or do ipconfig/release on a win2k box).
4. Try to read a message (you get 2 errors, both connection-related [why 2?
might be a seperate bug]).
5. Now, reconnect to the network by doing ipconfig/renew or dialing up.
6. Attempt to read messages.
Expected Results:
Messages, whether read or not, will display 100%.
Actual Results:
Especially in threads it seems, we are not reading from the cache correctly, or
invalidating from the cache. Screenshots to follow. One before shot, one after
shot.
Reporter | ||
Comment 1•24 years ago
|
||
Reporter | ||
Comment 2•24 years ago
|
||
Reporter | ||
Updated•24 years ago
|
OS: Windows 2000 → All
Hardware: PC → All
Reporter | ||
Comment 5•24 years ago
|
||
Reporter | ||
Comment 6•24 years ago
|
||
Hopefully, the log is helpful. Here are my steps to produce that log:
Messages "test123" and "test456" were unread messages. Message "there can only
be one" was a message I have already read.
1. In netscape.test, I read "test123" with my cable connection still alive.
2. Disconnected my connection, and attempted to read a read message ("there
can only be one").
3. Waited for timeout
4. Read "test456" (this didn't display correctly)
5. Read "test123", which finally loaded correctly.
Reporter | ||
Comment 7•24 years ago
|
||
Seems bug 59449's fix corrects this, or helps it tremendously. But I'll keep
testing.
Comment 8•24 years ago
|
||
it makes sense that the fix for #59449 fixes this, but I'll have to debug to
confirm.
I'd like to leave this bug open because I bet that when the connection gets
dropped we're leaking the protocol instance.
Updated•21 years ago
|
Product: MailNews → Core
Comment 9•18 years ago
|
||
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Comment 11•17 years ago
|
||
Can't reproduce -> WFM.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•