152374 - mozilla.exe process remains after mailto:[e-mail] is launched and closed

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking, defect)

Description

[Scott Copus]

Using Mozilla 1.1: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1a)
Gecko/20020611
on Windows XP Pro.

Executing (with Start, Run) a MAILTO:[e-mail], and then aborting
the message by clicking on the upper right-hand "X" close button will cause the
"mozilla.exe" process to remain in memory.  However, the File | Exit menu option
will close the mozilla.exe process.

This is a small bug, but annoying because it wastes memory and I don't know it's
running unless I use Task Manager and kill the process manually.

Comment 1

[Patrick Xia]

Reproducable on Mozilla "1.0" (Build 2002054012; windows XP; intel processor)

Comment 2

[Mike Cowperthwaite]

Confirming:
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
was also the case in 1.3 Final.

Note that this requires having Windows configured to use Mozilla to handle
mailto: links, a configuration that Mozilla currently does not make for itself.

Comment 3

[Mike Cowperthwaite]

btw, this almost certainly not a Front End bug, and probably not even a
Mail/News bug.  Maybe Networking:Mail/News General?

If it's a dupe, the other report is pretty obscurely worded.

Comment 4

[Mike Cowperthwaite]

A little more info: I have the network.protocol-hander.extern.mailto pref 
set to  False (re: bug 198547).  If I execute the mailto: link within Mozilla 
(click, or direct entry in the address bar), this symptom does not occur.  It 
occurs only if the mailto comes from another application.

Comment 5

[Mike Cowperthwaite]

I'm upgrading severity because this bug is a major pain when switching between a 
test version (1.4b nightly) and the standard version where I keep my mail.

I hope Networking:MailNews General is the appropriate component.

Comment 6

[Mike Cowperthwaite]

Between build 0430 and build 0506, this bug appears to have been squashed, 
probably as a side effect of the same fix that generated the side effect in Bug 
204752.  Any listeners to this bug might want to check this out, altho there are 
other problems with 0506 under Windows 98 (see Bug 204676).

Comment 7

[Mike Cowperthwaite]

This bug's "solution" is still in place with 1.4 Final, so I'm marking it 
WorksForMe.  It's quite possible that if bug 204752 gets fixed, this will come 
back, but I suspect not -- the solution to that bug will probably be part of the 
splitting of Mozilla into the component apps.