Closed Bug 313213 Opened 19 years ago Closed 19 years ago

STEP_TIMEOUT causes too much GC's.

Categories

(Other Applications :: ChatZilla, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Gijs, Assigned: rginda)

References

Details

(Whiteboard: [cz-0.9.69])

Attachments

(1 file)

858 bytes, patch
bugzilla-mozilla-20000923
: review+
Details | Diff | Splinter Review
According to Silver, we need a larger value for client.STEP_TIMEOUT in order to
get a few less GC's in js. This change has already been made in CZ 0.9.68.5

Patch coming up.
Attached patch PatchSplinter Review
Attachment #200295 - Flags: review?(silver)
I should work out just how much GCing it caused, but I remember debugging the JS engine and wondering why it was doing a GC so frequently, and it turned out to be the ChatZilla loop.

It doesn't actually allocate a lot of memory, but it causes a lot of small things to be allocated then freed (local variables, call stack, etc.), and SpiderMonkey uses the amount of memory "churn" [1] as a trigger for GCing.

[1] The amount of memory allocated since the counter was reset, ignoring frees.
Comment on attachment 200295 [details] [diff] [review]
Patch

r=silver

This will slow the client down, but since we already have the variable-speed code in at http://lxr.mozilla.org/seamonkey/source/extensions/irc/xul/content/static.js#1501 it should actually run at a decent speed still.
Attachment #200295 - Flags: review?(silver) → review+
checked in
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Whiteboard: [cz-0.9.69]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: