Closed
Bug 16662
Opened 26 years ago
Closed 25 years ago
TerminateProcess & TerminateThread
Categories
(Core :: XPCOM, defect, P3)
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: cparks, Assigned: rpotts)
References
()
Details
I thought you would be interested in knowing that your software has made the
Developer's Terminate Process & Terminate Thread Black List.
Updated•26 years ago
|
Assignee: don → rpotts
Component: Browser-General → Threading
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → REMIND
Target Milestone: M16
Comment 1•26 years ago
|
||
This is could be considered INVALID: the blacklist refers only to Released
software using TerminateProcess & TerminateThread that leak memory because
of their use of these two calls; in this case to Communicator.
On the other hand, perhaps this could be kept as a QA-tracking bug and given
a Target Milestone of 16 or so as a checkpoint to make sure that these
calls are removed prior to shipping.
(It is possible that XP threading code could call these indirectly through
an MFC dll for Win32 builds)
Marking M16 and REMIND; go ahead and INVALIDATE if this makes no sense.
| Assignee | ||
Comment 2•26 years ago
|
||
This is really an NSPR bug, since it deals with calls to the Win32 threading
API... I'm cc'ing larryh to let him know.
-- rick
Comment 4•25 years ago
|
||
http://lxr.mozilla.org/nspr/search?string=TerminatePro%2CTerminateThr®exp=on
shows exactly one use of TerminateProcess:
http://lxr.mozilla.org/nspr/source/nsprpub/pr/src/md/windows/ntmisc.c#553
in _PR_KillWindowsProcess
( http://lxr.mozilla.org/nspr/ident?i=_PR_KillWindowsProcess )
Following that trail, there does not seem to be any Seamonkey code that calls
_PR_KillWindowsProcess, so from the point of view of not using
the TerminateProcess & TerminateThread calls, Mozilla looks good.
Comment 5•25 years ago
|
||
adding Wan-Teh to the cc list.
Comment 6•25 years ago
|
||
We concur with comments by Sean Richardson.
NSPR does not provide a mechanism to kill threads. Killing a thread is (IMNSHO)
is a Bad-Thing. NSPR does provide a PR_KillProcess() function.
NSPR does not think this is a bug.
Comment 7•25 years ago
|
||
reopening and marking Future...
Status: RESOLVED → REOPENED
Resolution: REMIND → ---
Target Milestone: M16 → Future
Comment 8•25 years ago
|
||
Kill Process and Kill Thread is bad programming practice.
Marking WontFix.
Status: REOPENED → RESOLVED
Closed: 26 years ago → 25 years ago
Resolution: --- → WONTFIX
Comment 9•23 years ago
|
||
Moving all threading bugs to XPCOM. See bug 160356.
Component: Threading → XPCOM
You need to log in
before you can comment on or make changes to this bug.
Description
•