Closed
Bug 218697
Opened 21 years ago
Closed 21 years ago
[BEOS] Looper not always unlocked on a resize
Categories
(Core :: XUL, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: beos, Assigned: beos)
References
Details
(Keywords: hang)
Attachments
(1 file)
2.01 KB,
patch
|
sergei_d
:
review+
chofmann
:
approval1.6+
|
Details | Diff | Splinter Review |
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.
Comment 2•21 years ago
|
||
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+
Comment 3•21 years ago
|
||
Paul, will you ask approval to check it in before Mozilla 1.6b is out?
Keywords: hang
Comment 4•21 years ago
|
||
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?
Comment 5•21 years ago
|
||
CC-ing myself
Comment 6•21 years ago
|
||
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+
Comment 7•21 years ago
|
||
checkin by bz
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Comment 8•21 years ago
|
||
*** Bug 229272 has been marked as a duplicate of this bug. ***
Comment 9•21 years ago
|
||
*** 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.
Description
•