staff client patron search results continuously eats memory
Bug #1110817 reported by
Jason Etheridge
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Open the patron search interface and do a search that returns results (I used smith with the stock test data). No need to select a patron thus returned. Let the interface sit and watch the evergreen process slowly increase memory usage over time. My first suspect is exec.chain in search_result.js, though it shouldn't be running continuously.
Changed in evergreen: | |
status: | New → Triaged |
tags: | added: memoryleak |
tags: | added: staffclient |
Changed in evergreen: | |
importance: | Undecided → High |
status: | Triaged → Confirmed |
To post a comment you must log in.
Whatever it is, it doesn't appear to be util.exec. Galen mentioned that what it seems to be leaking is nsXPCWrappedJS( nsIDOMXULContro lElement ).