Closed
Bug 51384
Opened 25 years ago
Closed 23 years ago
Crash when navigating (deprecated?) relative URL's
Categories
(Core :: XUL, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jesup, Assigned: blizzard)
References
()
Details
(Keywords: crash)
Attachments
(2 files)
FreeBSD 4.1 20000905xx (noon EDT)
Crashes fairly consistently when navigating around the bug-test page for bug 50629.
Got to the URL. Click on "A http:/RFC link". Hit Back after you get to the
netscape search page. Click on "A /RFC/ link". Boom (usually).
The crash _appears_ to be occuring in nsWindow::UpdateIdle, perhaps in a
pure_virtual call.
2 stack backtraces to be appended.
Reporter | ||
Comment 1•25 years ago
|
||
Comment 2•25 years ago
|
||
Can't reproduce this crash on a build pulled ~2am last night (rh6.1 using gtk).
The stack traces, though, indicate that you are building with the xlib version
os nsWindow.cpp. pavlov says that quy@igelaus.com.au is one of the people
working on this. -> quy@igelaus.com.au
Assignee: trudelle → quy
Comment 3•25 years ago
|
||
erk, these arn't xlib stack traces. reassigning to blizzard, I'll take a look
at this
Assignee: quy → blizzard
Comment 4•25 years ago
|
||
Sorry, I was focussing on the line number in nsWindow.cpp, which must be
the xlib version (unless there is some confusion in the debugger dealing
with the symbols). [I should have made my question clearer ...]
Reporter | ||
Comment 5•25 years ago
|
||
Sorry, the line numbers (at least) are horked. Ever since I upgraded to FreeBSD
4.1 last week, GDB gives me bogus line numbers (and no arguments) for shared
libs. Weird. I _think_ the function names are good. (Yes, I did a full
clobber build after upgrading). This BSD thing happens to others too.
Reporter | ||
Comment 6•25 years ago
|
||
Nominating for nsbeta3. Crashes repeatably for me. We need confirmation it's
a problem with other platforms (or possibly a pull-while-tree-is-open issue).
More info on repeatability - I clicked on these links, waited until something
appears, click Back, try another one of them. After 2-7 visits of links on that
page, it crashes.
Comment 7•25 years ago
|
||
URL now "Not Found"
Comment 8•24 years ago
|
||
I just bumped into a very similar stack trace while looking at bug 65800 and bug
61386. I'm going to see if I can trace it any further, but this seems to still
be an issue. This is from a nightly build from 1/19/2001, with the patches from
the two previously mentioned bugs.
Comment 9•24 years ago
|
||
Comment 10•24 years ago
|
||
The procedure I followed to get this bug is the one in bug 66164. This is
completely different from the way that this bug was triggered initially (via
relative URLs). I don't know if relative URLs still crash.
Comment 11•24 years ago
|
||
Comment 12•24 years ago
|
||
The patches that fixed this for me have all landed. Somebody with more
knowledge of this bug than me (I have never been able to reproduce it) might
want to see if they can reproduce it, and go ahead and close it out...
Comment 13•24 years ago
|
||
404, no testcase, 'http:/' links are covered by another bug report.
Comment 14•23 years ago
|
||
I haven't experienced anything similar to this bug in nearly a year, and no
additional stack traces have been attached, and nothing's been marked as a
duplicate of this in over a year. Further, none of the examples (like visiting
an http:/ link) seem to trigger it anymore.
I think that somebody with the ability can probably safely close this bug out as
WORKSFORME.
Assignee | ||
Comment 15•23 years ago
|
||
Works for me, too.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•