Closed Bug 7365 Opened 27 years ago Closed 27 years ago

[PP]DeactiveTSMDocument Failed Assertion

Categories

(Core :: Layout: Form Controls, defect, P3)

PowerPC
Mac System 8.5
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: cyrus, Assigned: ftang)

References

Details

When switching to the console window, or attempting to start a new browser window, I sometimes see an assertion nsMacEventHandler::HandleActivateEvent. The assertion says "DeactivateTSMDocument Failed Assertion"
Component: Apprunner → Event Handling
OS: other → Mac System 8.5
QA Contact: leger → janc
Hardware: Other → Macintosh
Updating QA Contact
Assignee: don → tague
Component: Event Handling → Widget Set
Tague, this assertion appears to be added by you. Is this your bug or should Pierre deal with this?
Status: NEW → ASSIGNED
Depends on: 7571
The problem is that occasionally (not 100% reproduceable), the nsMacEventPump doesn't deliver the activate event to the nsMacEventHandler attached to the front window. I have TSMDocument activate and deactivate calls which run on that handler. The assertion happens when the calls get out of synch because of a missed activate event. I've removed the assertion for now at sfrasier's request, but I need to reactivate it later (meaning M9 or M10).
The problem is that occasionally (not 100% reproduceable), the nsMacEventPump doesn't deliver the activate event to the nsMacEventHandler attached to the front window. I have TSMDocument activate and deactivate calls which run on that handler. The assertion happens when the calls get out of synch because of a missed activate event. I've removed the assertion for now at sfrasier's request, but I need to reactivate it later (meaning M9 or M10).
Target Milestone: M8
CCd myself. This bug is probably related to #7571.
Summary: DeactiveTSMDocument Failed Assertion → [PP]DeactiveTSMDocument Failed Assertion
Moving all Widget Set bugs, past and present, to new HTML Form Controls component per request from karnaze. Widget Set component will be retired shortly.
Target Milestone: M8 → M9
moving to M10 to reflect bug fixing priorities
Target Milestone: M10 → M11
Target Milestone: M12 → M11
Move to M11. Tague, is this your bug ?
bulk reassign bugs to ftang for now
Status: NEW → ASSIGNED
Target Milestone: M11 → M12
Status: ASSIGNED → RESOLVED
Closed: 27 years ago
Resolution: --- → FIXED
fix when we check in 7571
verifried build 2001081308 os:mac8.6
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.