Closed
Bug 202679
Opened 22 years ago
Closed 22 years ago
[beos] each cursor change causes a "new" cursor to be created
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: beos, Assigned: beos)
Details
Attachments
(1 file)
With every change of the cursor, a "new" cursor is created on the heep. On some
machines, people have noticed this causing 100% cpu utilization.
patch to follow
Comment 2•22 years ago
|
||
Nice cacheing!
Only question, is NS_METHOD nsWindow::SetCursor(nsCursor aCursor) really best
place to fill array, or we can do it somewhere earlier?
Do you need review?
Comment 3•22 years ago
|
||
One stylish thing may be added, though, in nsBeOSCursors.h
# define NUM_OF_CURSORS 18
in order to ease programmers' life in case of future changes:)
But as we're adding each element separately, not inside loop, it will have
only mnemonical sense...
Comment on attachment 121096 [details]
now uses global array for storing cursors, instead of "new"ing all the time
The reason I loaded it in SetCursor, was that first, I knew it had to be done
before then, second, I wasn't sure putting it in the constructor would cause
problems. Plus, this gets called before the first window is shown, so it is
part of the "start-up" :-)
Attachment #121096 -
Attachment is patch: false
Attachment #121096 -
Flags: review?(sergei_d)
though have the define for the number of cursors would be nice, it is also not needed, as you already pointed out.
oh, and Sergei, to test regxpcom:
in dist/bin
run-mozilla.sh regxpcom
Comment 7•22 years ago
|
||
Comment on attachment 121096 [details]
now uses global array for storing cursors, instead of "new"ing all the time
r=sergei_d@fi.tartu.ee
Attachment #121096 -
Flags: review?(sergei_d) → review+
this has been checked in
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•