Closed Bug 72097 Opened 23 years ago Closed 17 years ago

opening file in composer takes a long time

Categories

(Core :: DOM: Editor, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME
mozilla1.5alpha

People

(Reporter: bugzilla, Unassigned)

References

()

Details

(Keywords: perf)

the editor takes an awfully long time to open a medium-sized file [about 80kb].

1. launched ./netscape -P [profile] -edit
2. clicked Open button to bring up file picker.
3. double-clicked the file in the URL [in my local tree] to open it.

result: it took 11 seconds to load the file --from the time i double-click its
name in the file picker to when i finally got a cursor. even subsequent attempts
to open the file [after exiting and restarting composer] take about 11sec.

this, imho, is way too long to wait: after all, i'm running 2001.03.12.12 comm
[modern theme] bits on a decently-spec'd linux box [HP Kayak 500Mhz PIII, 256M
RAM, Redhat 6.2 w/gnome desktop; running sawmill].
oops, almost forgot the url to the sample file.

also, this might be related to bug 29584 and bug 28783.
Severity: normal → major
Keywords: mozilla0.9, nsbeta1, perf
By the way, that page doesn't even load on a Mac with N6.
all kinds of code spits out in the window. someone may wanna
file a bug on this...
This page loads fine in my debug tip Mozilla build, and takes about 10 seconds. I 
don't see "all kinds of code spits out in the window".
I also tried on another Mac and it works fine...I will reinstall
the build on my mac...thanks Simon.
timings for win32 and mac:

* using 2001.03.19.09 comm verif bits on winNT, it took 9sec to open the file in
the editor. [also on a not-so-bad machine: HP Kayak, 500MHz PIII, 128M
RAMrunning winNT 4.0.]

* using 2001.03.19.12 comm verif bits on Mac OS 9.0, it took ~10sec to open the
file in the editor. [450MHz G3, 128M RAM.]

more info: i've been timing these using the modern theme, btw.
OS: Linux → All
Hardware: PC → All
this may be from populating all those empty table cells with br's, though i don't 
know why that would take 10 seconds.
moz1.0
Priority: -- → P3
Target Milestone: --- → mozilla1.0
Blocks: 92857
Blocks: 72677
Blocks: 104166
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
don't move bugs that are in the 1.0 dependency tree. sorry.

Target Milestone: mozilla1.0.1 → mozilla1.0
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+,
topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword.  Please send any
questions or feedback about this to adt@netscape.com.  You can search for
"Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
Target Milestone: mozilla1.2alpha → mozilla1.5alpha
Assignee: sfraser_bugs → mozeditor
QA Contact: sujay → bugzilla
WFM ~1sec http://www.mozilla.org/projects/ui/accessibility/mozkeylist.html

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060101 SeaMonkey/1.5a
QA Contact: bugzilla → editor
Assignee: mozeditor → nobody
=> WFM (trunk)
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.