Closed
Bug 84656
Opened 24 years ago
Closed 24 years ago
The treeview in Doxygen docu crashes the browser...
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: dothebart, Assigned: jst)
References
()
Details
Attachments
(4 files)
Generate the doxygen-Documentation for any project you can find a reference on
www.doxygen.org, using
"GENERATE_TREEVIEW = NO"
in the doxygen-Configuration.
Now the root of the documentation is presented to you in a frameset.
on the left frame, there is a Treeview containing all classes for your
project,the main Frame shows the usual Doxygen-Start-Page.
In the tree-View you are able to select classes et.
Also anoying is, that it starts with open folders, and if you have lots of
subelements (classes types etc.) this gets verry unhandy.
Netscape 4* does this with closed folders from the beginnig, so you can
browse the tree as it is usefull for you.
In M6 it was just horribly slow, but from M7 it started blocking the browser.
Comment 1•24 years ago
|
||
Browser, not engine --> Layout
Assignee: rogerl → karnaze
Component: Javascript Engine → Layout
QA Contact: pschwartau → petersen
Comment 2•24 years ago
|
||
willi@7val.de - could you attach a page which crashes the browser to this bug,
using the "Create a new attachment" link above?
Gerv
Severity: blocker → critical
| Reporter | ||
Comment 3•24 years ago
|
||
| Reporter | ||
Comment 4•24 years ago
|
||
| Reporter | ||
Comment 5•24 years ago
|
||
| Reporter | ||
Comment 6•24 years ago
|
||
willi@7val.de, could you please give a detailed description, where the critical
site cana be found at www.doxygen.org. I am unable to understand your problem
when viewing your attachments seperately. Probably my fault;)
| Reporter | ||
Comment 8•24 years ago
|
||
no, I can't. Sorry, if I repeat myself... I didn't find any project using
doxygen, showig their Dokumentation in the web using the frameset.
with the Apendixes: the first one should load the two java-Script files,
and then mozilla should crash.
So if I click on the first attachment (06/13/01 04:40) I just get a blank page,
which contains the following code [View | Page Source]:
<html><head>
<link rel="stylesheet" href="doxygen.css">
<script src="treeview.js"></script>
<script src="tree.js"></script>
<script>
initializeDocument()
</script>
</head>
<body bgcolor="#ffffff">
</body>
</html>
This doesn't crash my browser, but the Java-Script isn't executed, too. What am
I doing wrong to reproduce the bug?
| Reporter | ||
Comment 10•24 years ago
|
||
Does this help?
#0 0x4014d609 in nsAString::do_AppendFromReadable () from
/usr/local/mozilla92/./libxpcom.so
#1 0x4014cea7 in nsAString::AppendFromReadable () from
/usr/local/mozilla92/./libxpcom.so
#2 0x40c8c99f in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#3 0x40c8caf6 in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#4 0x40c8e035 in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#5 0x40c91aa3 in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#6 0x408e3c52 in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#7 0x408e0a72 in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#8 0x408e15d6 in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#9 0x408dffda in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#10 0x408df1eb in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#11 0x408f31d3 in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#12 0x408f2f91 in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#13 0x408f2ccc in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#14 0x40c9e3df in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#15 0x40c9eaae in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#16 0x40c9ec8e in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#17 0x40143061 in XPTC_InvokeByIndex () from /usr/local/mozilla92/./libxpcom.so
#18 0x40717029 in NSGetModule () from
/usr/local/mozilla92/components/libxpconnect.so
#19 0x4071c515 in NSGetModule () from
/usr/local/mozilla92/components/libxpconnect.so
#20 0x400753e5 in js_Invoke () from /usr/local/mozilla92/./libmozjs.so
#21 0x4007cc42 in js_Interpret () from /usr/local/mozilla92/./libmozjs.so
#22 0x4007582f in js_Execute () from /usr/local/mozilla92/./libmozjs.so
#23 0x40059c75 in JS_EvaluateUCScriptForPrincipals () from
/usr/local/mozilla92/./libmozjs.so
#24 0x40acdb2f in NSGetModule () from /usr/local/mozilla92/components/libjsdom.so
#25 0x40db3c31 in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#26 0x40db38ab in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#27 0x40db3657 in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#28 0x40c734bd in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#29 0x40c3f23a in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#30 0x40c95835 in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#31 0x40c91bf9 in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#32 0x408e43b7 in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#33 0x408e44af in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#34 0x408e15bd in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#35 0x408dffda in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#36 0x408df1eb in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#37 0x408f31d3 in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#38 0x408f2f91 in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#39 0x408f26b5 in NSGetModule () from /usr/local/mozilla92/components/libhtmlpars.so
#40 0x40c9546b in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#41 0x40db3a6a in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#42 0x40db38b8 in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#43 0x40db4a04 in NSGetModule () from
/usr/local/mozilla92/components/libgkcontent.so
#44 0x40850fc0 in NSGetModule () from /usr/local/mozilla92/components/libnecko.so
#45 0x4085593a in NSGetModule () from /usr/local/mozilla92/components/libnecko.so
#46 0x40876b1b in NSGetModule () from /usr/local/mozilla92/components/libnecko.so
#47 0x40889bc8 in NSGetModule () from /usr/local/mozilla92/components/libnecko.so
#48 0x40845d98 in NSGetModule () from /usr/local/mozilla92/components/libnecko.so
#49 0x4012fff7 in PL_HandleEvent () from /usr/local/mozilla92/./libxpcom.so
#50 0x4012ff13 in PL_ProcessPendingEvents () from /usr/local/mozilla92/./libxpcom.so
#51 0x40130ea8 in nsEventQueueImpl::ProcessPendingEvents () from
/usr/local/mozilla92/./libxpcom.so
#52 0x4075b9a3 in NSGetModule () from
/usr/local/mozilla92/components/libwidget_gtk.so
#53 0x4075b71d in NSGetModule () from
/usr/local/mozilla92/components/libwidget_gtk.so
---Type <return> to continue, or q <return> to quit---»
#54 0x4036cc40 in g_io_add_watch () from /usr/lib/libglib-1.2.so.0
#55 0x4036e309 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#56 0x4036e913 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#57 0x4036eaac in g_main_run () from /usr/lib/libglib-1.2.so.0
#58 0x40282c57 in gtk_main () from /usr/lib/libgtk-1.2.so.0
#59 0x4075be9c in NSGetModule () from
/usr/local/mozilla92/components/libwidget_gtk.so
#60 0x4073e83a in NSGetModule () from
/usr/local/mozilla92/components/libnsappshell.so
#61 0x804e9e4 in main1 ()
#62 0x804f225 in main ()
#63 0x404aa2db in __libc_start_main () from /lib/libc.so.6
| Reporter | ||
Comment 11•24 years ago
|
||
if not, may I send one of you a tgz whith a doxygen-docu?
Comment 12•24 years ago
|
||
Going to go ahead and Mark NEW but this looks a lot like bug 78708 which was
marked a dupe of a bug that was marked WORKSFORME. So go figure.
| Reporter | ||
Comment 13•24 years ago
|
||
still blocks instantly with 0.92.
Comment 15•24 years ago
|
||
Er, wrong kind of |tree|. This is building some kind of tree structure with DOM
methods in JS.
With the four attached files, on win2k, I get locked up in layout/content
code for several minutes before the page is shown, although I don't crash.
However, I don't really understand what the original steps to reproduce this
crash are supposed to be. Wilfried, can you elaborate some more on just
where/what it is that you are doing?
At any rate, this isn't hyatt's. -> jst, cc: attinasi
Assignee: hyatt → jst
| Reporter | ||
Comment 16•24 years ago
|
||
Well, with the example it may tage several minutes, with a real documentation
(that would contain at about 100 or more nodes in the Tree) it could take hours...
forgive me that I didn't wait for it ;-)
what I was doing:
*taking doxygen-programm documentation (way of similar to Perldoc, Javadoc, qt...)
*taking some projects that contain Javadoc
*letting Javadoc produce it's html-output with a framed Index-page
*watch it through apache
*get stuck :-(
if you want a real-life Environment, get doxygen from www.doxygen.org,
gett one of the numerous (on the website mentioned)projects using doxygen,
let doxygen give you a sample-configuration, modify this to your needs (and say
that it should use frames) push the files to a Webserver, and enjoy your two
minutes (if that's what it takes ;-)
| Assignee | ||
Comment 17•24 years ago
|
||
Is this still crashing mozilla?
Comment 18•24 years ago
|
||
I put the four attachments at http://jrgm.mcom.com/bugs/84656/page.html, and
supplied the required images (well, just gave it an image).
It doesn't crash for me (didn't before). It does take a long time (about 45
seconds in a trunk build now).
However, it takes about that long in Nav4.x, and, while somewhat less in IE,
IE throws up a 'long running script' warning [Cancel|Continue] while it is
processing the page.
In other words, no browser can usefully make use of the content in the
example given.
Severity: critical → normal
Keywords: crash
| Assignee | ||
Comment 19•24 years ago
|
||
Marking WONTFIX, this should get faster as random performance improvments are
made in mozilla, but there doesn't seem to be a specific bug here.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•