Summary: | Long time running Eclipse RCP causing SWTException | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Guanghong <gyang> |
Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | Carolyn_MacLeod, eclipse.felipe, gheorghe, steve_northover |
Version: | 3.4.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Guanghong
2009-04-03 21:17:24 EDT
Does it work if you run the failure test alone ? Maybe try a different VM or a different version of SWT (ie. SWT 3.5 M6) ? Steve, any ideas what can be the problem ? I see Display.runSettings() on the stack. This means that a system setting was getting changed sometime during the execution of the RCP application. The line in CTabFolderLayout.layout() is bogus: Control control = folder.items[folder.selectedIndex].getControl(); if (control != null && !control.isDisposed()) { control.setBounds(folder.getClientArea()); } It uses API to the control, then test for it being disposed. If the control can be disposed, then the getControl() will fail. The question is, when a control is disposed in a CTabFolder, do we attempt to clean it up from the CTabFolderItem or just check for a disposed control everytime we access it? Someone needs to look at the code, decide and then fix all places 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. |