Closed
Bug 214363
Opened 22 years ago
Closed 22 years ago
Assertion in mozilla/content/base/src/nsRange.cpp
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 214343
People
(Reporter: tenthumbs, Unassigned)
Details
Taking a wild guess as to component ...
With my Linux trunk build from this morning, I go to the bugzilla query page,
enter a query, press submit and I get this:
Document http://bugzilla.mozilla.org/query.cgi loaded successfully
###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 840
Break: at file nsRange.cpp, line 840
###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 840
Break: at file nsRange.cpp, line 840
###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 840
Break: at file nsRange.cpp, line 840
###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 840
Break: at file nsRange.cpp, line 840
###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 840
Break: at file nsRange.cpp, line 840
###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 840
Break: at file nsRange.cpp, line 840
###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 840
Break: at file nsRange.cpp, line 840
###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 840
Break: at file nsRange.cpp, line 840
###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 840
Break: at file nsRange.cpp, line 840
###!!! ASSERTION: nsRange::IsIncreasing: 'Not Reached', file nsRange.cpp, line 840
Break: at file nsRange.cpp, line 840
The code is:
if (startIdx == endIdx) {
// whoa nelly. this shouldn't happen.
NS_NOTREACHED("nsRange::IsIncreasing");
}
Note that the security warning dialog pops up when I press submit. It's what I
want. I doubt it's relevant, though.
This is a new feature.
![]() |
||
Comment 1•22 years ago
|
||
This is the same as bug 214343 -- range stuff got generally sorta broken. Patch
in that bug fixes this issue.
*** This bug has been marked as a duplicate of 214343 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•