Closed Bug 3465 Opened 26 years ago Closed 26 years ago

[BLOCK] setAttribute calls fail intermittently (but persistently)

Categories

(Core Graveyard :: Tracking, defect, P1)

Product:
Core Graveyard
Component:
Tracking
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: law, Assigned: waterson)

References

(
URL
)

Details

I can only do a limited number of setAttribute calls (from JS or from C++) on an
nsXULDocument until I get a crash.  The crash occurs deep in RDF, apparently.

This bug is Public Enemy #1.
Assignee: hyatt → don
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Status: REOPENED → NEW
Resolution: WORKSFORME → ---
Assignee: don → waterson
Re-assigned to waterson@netscape.com.

Chris, is this your bug or hyatt's bug?
Status: NEW → ASSIGNED
This bug is so much my bug that I could cry. Hyatt (or somebody) needs to send
me the test case.
URL: resource:/res/samples/status.xul
You can use the status.xul file I just updated and referenced from the URL field
above.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
Modified nsRDFService to atomize literals as well as resources. This was
causing problems in the in-memory data source: it couldn't keep a proper
"reverse-arcs" map when a with the same value could have several
implementations.
If this is fixed with Mar 09 build, could you mark verified?  Thanks!
Status: RESOLVED → VERIFIED
Moving all Apprunner bugs past and present to Other component temporarily whilst
don and I set correct component.  Apprunner component will be deleted/retired
shortly.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.