Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 345052

Summary: [Mac OS X] UI freezes while waiting for browser to load
Product: [Eclipse Project] Platform Reporter: Stefan Mücke <s.muecke>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: falko.schumann
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard: stalebug
Attachments:
Description Flags
Snippet to reproduce the bug none

Description Stefan Mücke CLA 2011-05-07 04:30:00 EDT
Created attachment 195002 [details]
Snippet to reproduce the bug

Build id: I20110428-0848 (Eclipse 3.7 M7)

Sometimes it is necessary to load browser content synchronously. This is done by spinning the event loop until a ProgressEvent 'completed' is received. Such code is found, for example, in the BrowserInformationControl (JFace). On Mac OS X, there is a bug that may cause the UI to freeze.

Steps to reproduce:

1. Run the attached FreezeBug.java
2. Double-click a list item before the browser
   completes to load (if computer is too fast,
   increase the 'paragraphCount')
3. Scroll the list back and forth with the mouse wheel
   --> UI is freezed; no scrolling occurs
4. Click the list
   --> UI wakes up and tries to catch up
   --> list wildly scrolls and UI freezes again

I can also reproduce this bug in 3.6.2, but not in 3.5. This broke my RCP application when I tried to migrate from 3.5 to 3.7 M7. On Windows, everything is fine.
Comment 1 Stefan Mücke CLA 2011-05-07 04:47:08 EDT
Addendum:
  Mac OS X Version 10.5.8, Cocoa, 32-bit
  Java 1.5.0_28
Comment 2 Lars Vogel CLA 2019-11-14 03:38:20 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.