Closed
Bug 3537
Opened 26 years ago
Closed 25 years ago
NSPR shouldn't call Delay()
Categories
(NSPR :: NSPR, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: gordon, Assigned: sdagley)
Details
Chris Saari believes that NSPR needs to call WaitNextEvent() instead of Delay().
Additional code may be necessary to prevent certain events from getting lost,
such as AppleEvents. Also, this might not be desired for all threads.
Updated•26 years ago
|
Assignee: wtc → gordon
Comment 1•26 years ago
|
||
Reassigned the bug to gordon.
Comment 2•26 years ago
|
||
You won't loose events if you give WaitNextEvent a null event mask. In other
words, you're not really retrieving the next event, you're yeilding time to the
system which Delay() doesn't do.
Delay() is evil. It is a spin loop on a non-preemptive system. Nothing can happen
during a Delay() call.
Comment 4•25 years ago
|
||
NSPR now has its own Bugzilla product. Moving this bug to the NSPR product.
Assignee | ||
Updated•25 years ago
|
Assignee: gordon → sdagley
Status: ASSIGNED → NEW
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•25 years ago
|
||
Fix is checked in.
Note to QA - you can't really test this other than looking at the source for /
mozilla/nsprpub/ps/src/md/mac/macio.c.
Updated•24 years ago
|
Target Milestone: M9 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•