Closed Bug 482904 Opened 15 years ago Closed 3 years ago

Unclear relationship between MAX_MALLOC_BYTES and MAX_BYTES

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: gyuyoung, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ko; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
Build Identifier: 

Currently, tracemonkey has two counters for the memory allocation. One is gcMaxBytes, the other is gcMaxMallocBytes. According to my investigation, the role of gcMaxBytes is to count memory allocation for GC and the gcMaxMallocBytes's is to count memory allocation for malloc().For example, JS_malloc(). It seems we need to verify each role correctly and to find a way to merge the two counters into a counter.

Reproducible: Always
Assignee: general → nobody

Old bug, no longer valid.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.