Consolidate calls to nsISHEntry::GetChildAt
Categories
(Core :: DOM: Navigation, enhancement, P2)
Tracking
()
Fission Milestone | M2 |
People
(Reporter: annyG, Assigned: annyG)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
Updated•7 years ago
|
Assignee | ||
Updated•7 years ago
|
Assignee | ||
Comment 1•7 years ago
|
||
I changed the bug description as we realized that nsISHistory::RemoveEntries is in the parent process already.
Assignee | ||
Comment 2•7 years ago
|
||
Assignee | ||
Comment 3•7 years ago
|
||
Currently, nsDocShell repeatedly calls nsISHEntry::GetChildAt and
nsISHEntry::RemoveChild in nsDocShell::AddToSessionHistory,
which results in twice as many IPC calls as the number of children
a session history entry has. Additionally, there is one extra
IPC sync call to nsISHEntry::AbandonBFCacheEntry after the loop.
With the proposed solution, there will only be 1 sync IPC call.
Depends on D24977
Assignee | ||
Comment 4•7 years ago
|
||
Currently, nsDocShell repeatedly calls nsISHEntry::GetChildAt, which
results in as many IPC sync calls as the number of children
a session history entry has. Calling nsISHEntry::GetChildCount
and ChildSHistory::LEgacySHistory::RemoveEntries incurs additional
extra 2 sync IPC calls.
With the proposed solution, there will only be 1 sync IPC call.
Assignee | ||
Updated•7 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Comment 5•6 years ago
|
||
Pushed to ash branch:
https://hg.mozilla.org/projects/ash/rev/3f4a092d8f6544a212ee8a80d9275ae68c6446d1
https://hg.mozilla.org/projects/ash/rev/b081ebe7b3f52dec2a85e744b2dd2a4b0f344f8e
https://hg.mozilla.org/projects/ash/rev/0270d6b952ffa1704690c777c55fcaed30125b38
![]() |
||
Comment 7•6 years ago
|
||
bugherder |
Description
•