Closed
Bug 468347
Opened 17 years ago
Closed 16 years ago
Use native JSON support for parsing JSON, if available
Categories
(Webtools Graveyard :: Graph Server, defect, P3)
Webtools Graveyard
Graph Server
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bzbarsky, Unassigned)
Details
(Keywords: perf)
A lot of the beachballing graph server causes seems to be due to its JSON parsing. We should look into using the native JSON support Gecko has nowadays to do this faster.
|
||
Updated•17 years ago
|
OS: Mac OS X → All
Hardware: PC → All
|
||
Updated•17 years ago
|
Assignee: nobody → ccooper
Priority: -- → P2
|
|
||
Updated•17 years ago
|
Status: NEW → ASSIGNED
|
|
||
Comment 1•17 years ago
|
||
Can I get some specific examples of the beachballing? It will help me gauge progress.
|
|
Reporter | |
Comment 2•17 years ago
|
||
STEPS TO REPRODUCE:
1) Load http://graphs.mozilla.org/
2) Select "Tp3" in the test dropdown
3) Click "Add All"
I killed my browser about 7 minutes later; in the meantime it was completely frozen up (though it took a bit to get there). You might want to restrict to trunk only or something if you want to have a shorter freeze.
|
|
||
Comment 3•17 years ago
|
||
Hasn't JSON.jsm been removed in 3.1? Or is there another module I should be looking at?
|
||
Comment 4•17 years ago
|
||
https://developer.mozilla.org/En/Using_JSON_in_Firefox talks about how to use the native JSON object. You'll want to use the library if the native JSON isn't present (FF < 3.1, IE < 8)
|
|
||
Comment 5•17 years ago
|
||
Throwing this one back in the pool. I haven't found the time to work on it.
Assignee: ccooper → nobody
Status: ASSIGNED → NEW
Priority: P2 → P3
|
|
||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
|
Assignee | |
Updated•9 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•