Community
Participate
Working Groups
Build Identifier: 3.7.1 We are using Tables in several places in our UI (pure Java & SWT). From several users we get reports of IOOBE (trace below), where our app is not directly on the stack. The IOOBE happens on several of the tables, in the trace below, the table has 4 columns. It does not happen to all Windows users, some are affected heavily, others not. Unfortunately we could not reproduce on our machines. Any Idea? I don't understasnd what is happening at that place, but assume it is the column index that is out of bounds. BTW, this happened already with 3.6.2, hoping it would be fixed in 3.7.1 did not help unfortunately. Reproducible: Sometimes Steps to Reproduce: Trace: java.lang.ArrayIndexOutOfBoundsException: 4 at org.eclipse.swt.widgets.Table.wmNotifyChild(Table.java:6743) at org.eclipse.swt.widgets.Control.wmNotify(Control.java:5534) at org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:1896) at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:5086) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4584) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2425) at org.eclipse.swt.widgets.Table.callWindowProc(Table.java:564) at org.eclipse.swt.widgets.Table.callWindowProc(Table.java:430) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623) at org.eclipse.swt.widgets.Table.windowProc(Table.java:5893) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) at org.eclipse.swt.internal.win32.OS.PeekMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.PeekMessage(OS.java:3114) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3749)
My stack trace is unfortunately from a user running windows 7, but seems to be the same error. org.eclipse.swt.SWTException:+Failed+to+execute+runnable+(java.lang.ArrayIndexOutOfBoundsException:+4) at+org.eclipse.swt.SWT.error(Unknown+Source) at+org.eclipse.swt.SWT.error(Unknown+Source) at+org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown+Source) at+org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown+Source) at+org.eclipse.swt.widgets.Display.readAndDispatch(Unknown+Source) at+Main.<init>(Main.java:99) at+Main.main(Main.java:31) Caused+by:+java.lang.ArrayIndexOutOfBoundsException:+4 at+org.eclipse.swt.widgets.Table.wmNotifyChild(Unknown+Source) at+org.eclipse.swt.widgets.Control.wmNotify(Unknown+Source) at+org.eclipse.swt.widgets.Composite.wmNotify(Unknown+Source) at+org.eclipse.swt.widgets.Control.WM_NOTIFY(Unknown+Source) at+org.eclipse.swt.widgets.Control.windowProc(Unknown+Source) at+org.eclipse.swt.widgets.Canvas.windowProc(Unknown+Source) at+org.eclipse.swt.widgets.Decorations.windowProc(Unknown+Source) at+org.eclipse.swt.widgets.Shell.windowProc(Unknown+Source) at+org.eclipse.swt.widgets.Display.windowProc(Unknown+Source) at+org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native+Method) at+org.eclipse.swt.internal.win32.OS.CallWindowProc(Unknown+Source) at+org.eclipse.swt.widgets.Table.callWindowProc(Unknown+Source) at+org.eclipse.swt.widgets.Table.callWindowProc(Unknown+Source) at+org.eclipse.swt.widgets.Control.windowProc(Unkn
One of our customers ran into this problem with our software. It turns out to be a problem with AVG Antivirus's "Identity Protection" feature. You can fix it by disabling that feature, or upgrading to the latest version of AVG. See: http://forums.avg.com/in-en/avg-forums?sec=thread&act=show&id=175473
Thanks Cody, in fact the amount of reports has decreased significantly since about October 6th (the AVG update was on 5th, I think). I thus close this issue (reopen if you disagree).
