99647 - quick launch remembering mail info from one profile to another.

Status: VERIFIED WORKSFORME

(MailNews Core :: Backend, defect, P5)

Description

[jlarsen]

1. Have quick launch open
2. Open profile, into mail/news.
3. Put something in local folder/drafts, or any folder/newsgroup shared among
multiple profiles.
4. Close mozilla. (with quick launch still open)
5. Open new profile.
6. Item will be there.
7. close and completly quit quick launch. 
8. Open profile in 5.
9. Item will be gone.

Comment 1

[jlarsen]

*** Bug 99644 has been marked as a duplicate of this bug. ***

Comment 2

[David :Bienvenu]

we don't support sharing folders across profiles like this. When you say item,
do you mean a message? Is the message there when you go back to the first
profile? And what do you mean "not there"? Have you opened the folder to see
it's not there? Or are you saying that the message count for the folder is not
correct (doesn't reflect the new message count)?

Comment 3

[jlarsen]

What I'm saying is that if any two profiles have folders of the same name, (can
be a pop or local folder not sure about imap or newsgroup havn't tested). If you
switch profiles with the new ability in quick launch to do so without exiting
quick launch. The messages in the folder of the previous profile appear in the
new profile. They don't get saved to the new profile luckly so if you quit and
restart they are gone, but some memory variables obviously arn't getting
flushed. The most obvious example would probably be to quit a profile, and
create a new profile with same pop info, you will see the entire inbox
replicated. Thats how I discoverd, very creapy.

Comment 4

[David :Bienvenu]

OK, I see what you mean - does this mainly happen for newly created folders? It
might be that we're leaking the rdf resource (cc'ing Navin).

Comment 5

[jlarsen]

no, doesn't have to be newly created, just two profiles that have same folder
names, thats why I gave the example as local folder, because all profiles use one.

Comment 6

[David :Bienvenu]

I'm pretty sure this is a dup of one of several quicklaunch bugs that have been
fixed recently, so I'm marking it wfm.

Comment 7

[esther]

verifying as wfm, it is actually a dup of 138217 which is resolved fixed.  Note:
138217 has not been verified as fixed but that bug has current information and
will be the bug for monitoring this scenario now.