Closed
Bug 19170
Opened 25 years ago
Closed 25 years ago
Need to yield to necko thread more often
Categories
(Core :: Networking, defect, P3)
Tracking
()
VERIFIED
FIXED
M12
People
(Reporter: sfraser_bugs, Assigned: sfraser_bugs)
Details
There are performance problems now (e.g. image rendering 18738) which result from
us not yielding to the necko thread often enough. We need to yield every time
through the main event loop.
Assignee | ||
Comment 1•25 years ago
|
||
Patch for this (line numbers omitted, because I have other changes)
DoIdle(*anEvent);
if (mRunning)
Repeater::DoIdlers(*anEvent);
+
+ // yield to other threads
+ PR_Sleep(PR_INTERVAL_NO_WAIT);
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•25 years ago
|
||
Fix checked in.
Assignee | ||
Comment 3•25 years ago
|
||
This change should make rendering of large image snappier. It should also help
other stuff that runs on threads, like IMAP.
Comment 4•25 years ago
|
||
this smells like something that may be hurting unix too.
adding mscott, pavlov and alecf to the cc list.
anyone have ideas how to do this on unix, too?
the fix was to
Comment 5•25 years ago
|
||
add me to the cc list too.
Comment 6•25 years ago
|
||
ok, I'm trying a similar fix for unix now...
cross your fingers, unix lovers!
Index: nsWidget.cpp
===================================================================
RCS file: /cvsroot/mozilla/widget/src/gtk/nsWidget.cpp,v
retrieving revision 1.168
diff -p -r1.168 nsWidget.cpp
*** nsWidget.cpp 1999/11/16 01:10:46 1.168
--- nsWidget.cpp 1999/11/18 06:22:22
*************** NS_IMETHODIMP nsWidget::DispatchEvent(ns
*** 1324,1329 ****
--- 1324,1332 ----
}
NS_RELEASE(aEvent->widget);
+ // yield to other threads
+ PR_Sleep(PR_INTERVAL_NO_WAIT);
+
return NS_OK;
}
Bulk move of all Necko (to be deleted component) bugs to new Networking
component.
Comment 9•25 years ago
|
||
setting milestone and marking verified
Status: RESOLVED → VERIFIED
Target Milestone: --- → M12
You need to log in
before you can comment on or make changes to this bug.
Description
•