Closed Bug 218697 Opened 21 years ago Closed 21 years ago

[BEOS] Looper not always unlocked on a resize

Categories

(Core :: XUL, defect)

x86
BeOS
defect
Not set
major

Tracking

()

RESOLVED FIXED

People

(Reporter: beos, Assigned: beos)

References

Details

(Keywords: hang)

Attachments

(1 file)

Under normal use, mozilla will resize normally, since resize events are initiated via the user actually resizing the window. However, if mozilla initiates the resize events (i.e. going into "fullscreen" mode), the looper gets into an locked state, causing mozilla to hang. This is caused by a, what we thought was working, modification to the Move/Resize code, and us trying to reduce the number of locks/unlocks to the looper. The patch to follow will remove the non-working optimization.
This should fix the problem of going into fullscreen mode
Comment on attachment 131111 [details] [diff] [review] patch to remove "non-working" optimization keyword must be "hang" severity seems higher than "normal"
Attachment #131111 - Flags: review+
Paul, will you ask approval to check it in before Mozilla 1.6b is out?
Keywords: hang
Comment on attachment 131111 [details] [diff] [review] patch to remove "non-working" optimization asking approval for this hang/freeze bug. (it was regression, and patch returns to proven code) As port-only (BeOS) patch it seems don't require sr
Attachment #131111 - Flags: approval1.6?
CC-ing myself
Comment on attachment 131111 [details] [diff] [review] patch to remove "non-working" optimization yes, ok to check in for 1.6 --chofmann
Attachment #131111 - Flags: approval1.6? → approval1.6+
checkin by bz
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
*** Bug 229272 has been marked as a duplicate of this bug. ***
*** Bug 225716 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: