Open Bug 222051 Opened 21 years ago Updated 2 years ago

Please speed up mozilla -remote

Categories

(Toolkit :: Startup and Profile System, enhancement, P3)

x86
Linux
enhancement

Tracking

()

REOPENED

People

(Reporter: greenrd, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: perf, Whiteboard: [ts])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925

Sometimes launching a page from another app with mozilla -remote causes a lot of
paging and a few seconds delay. This gets irritating if you use it a lot. I only
have 128Mb RAM on this system and a lot of stuff running sometimes. Using a FIFO
or something, it should be possible to make mozilla -remote really really fast
and efficiently.

Reproducible: Always

Steps to Reproduce:
The startup script in the rpms actually calls the super-lightweight client
program which doesn't have this problem.
The search for windows with a WM_STATE atom and amongst those for matching mozilla atoms can take up ~ 0.6 seconds of start up time on my system when there are many windows.  I expect it would be much more for remote connections.

It's probably worth seeing if this can be optimized.

It seems that not all window hierarchies rooted at children of the root window have WM_STATE atoms.  I don't know how much checking every window in these hierarchies contributes to the overall time.
Keywords: perf
Whiteboard: [ts]
Blocks: 447581
Mass resolving a bunch of old bugs in the x-remote component in preparation for archiving it. If this bug is still valid and useful, please move it to the "Toolkit: Startup and Profile System" component and reopen it.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Component: X-remote → Startup and Profile System
Product: Core → Toolkit
Resolution: INCOMPLETE → ---
Priority: -- → P3
Assignee: blizzard → nobody
QA Contact: blizzard
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.