Community
Participate
Working Groups
I have an intermitent problem that occurs when I try to maximize the console view (it also occurs sometimes when I try to view java source code). I get the following pop-up messag box: Internal Error An internal error has occurred. Argument not valid. See error log for more details. The window title bar appears in maximized form but only a small rectangle of text gets drawn mid-screen (the area underneath where the pop-up message box was after I click OK). I can usually view the rest of the text by 'selecting' it with the mouse, although I get the error message again and again. I am runnig WSAD 4.03under Windows 2000 Advanced Server at 1280x1024 resolution. Log entry follows: Log: Thu Apr 04 18:11:13 EST 2002 4 org.eclipse.ui 0 Argument not valid java.lang.IllegalArgumentException: Argument not valid at org.eclipse.swt.SWT.error(SWT.java:1695) at org.eclipse.swt.SWT.error(SWT.java:1642) at org.eclipse.swt.graphics.GC.drawImage(GC.java:675) at org.eclipse.swt.custom.StyledText.handlePaint(StyledText.java(Compiled Code)) at org.eclipse.swt.custom.StyledText$13.handleEvent(StyledText.java:4252) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Compiled Code)) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Compiled Code)) at org.eclipse.swt.widgets.Composite.WM_PAINT(Composite.java(Compiled Code)) at org.eclipse.swt.widgets.Control.windowProc(Control.java(Compiled Code)) at org.eclipse.swt.widgets.Display.windowProc(Display.java(Compiled Code)) at org.eclipse.swt.internal.win32.OS.DispatchMessage(Native Method) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code)) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled Code)) at org.eclipse.ui.internal.Workbench.run(Workbench.java:656) at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav a:815) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285) at java.lang.reflect.Method.invoke(Native Method) at org.eclipse.core.launcher.Main.basicRun(Main.java:151) at org.eclipse.core.launcher.Main.run(Main.java:442) at org.eclipse.core.launcher.Main.main(Main.java:315)
Not sure why the GC.drawImage causes problems. It only throws an IllegalArgumentException when the Image that is passed in is disposed. We create the image just a few lines above the problem location so that's not really possible. Verified that drawing at a negative location is not a problem.
When you maximize the console and the error occurs, do you see any common pattern? For example do you always have a lot of text in the console or a lot of long lines or maybe the console is always scrolled to the bottom or to the very top. Is your workbench itself maximized when you maximize the console? I'm looking for something to give me clue what to look for. Unfortunately the stack trace is not very helpful in this case. Can you provide more detail under what circumstances you see the error in the Java editor? Is it the exact same stack trace as in the console maximize problem?
Created attachment 572 [details] Log file
I can recreate the problem even with an empty console window (i.e. no text). Log (attached to bug as separate activity) is from starting product then switching immeditately to java perspective and maximizing empty console window. I now note a few 'startup' errors in the log but don't know whether they are releated or not. I am running at 1280x1024. (I *cannot* recreate the problem at 1024x768). The problem is not restricted to having the workbench maximized. HOWEVER, through experimentation, I have discovered the following: at 1280 horizontal, it is okay at 720, error at 721. If I decrease the horizontal size to, for example, 1196, I am okay at vertical 758 but fail at vertical 760. Unfortunatley, these results are not 100% consistent (it occasionally works when it seems it shouldn't). The number of open perspectives and source windows does not seem to make a difference. Some analysis: At 1280 horizontal, works at 720 v. (921,600 total pixels) but fails at 721 v. (922,880 total pixels). At 1196 horizontal, works at 758 v. (906,598 total pixels but fails at 760 v. (908,960 total pixels). So... it's not simply a buffer size issue. There is no consistency in the ratio (horizontal to vertical) at which failure occurs. The failure point does seem to consistently be when WSAD occupies somewhere between 60 and 70% (or more) of the total real estate, although this is probably coincidental. I will attach an Excel spreadsheet that contains my analysis to the bug as well.
Created attachment 573 [details] Error test analysis
Not surprisingly, also happens when running at 1600x1200 resolution.
Thanks for the data, you're great! Unfortunately I still can't reproduce the problem. I wrote a test case that draws a 1280x952 (= 1024 - trim) buffered bitmap to the screen at 32bit color depth and it works fine. I also ran the current Eclipse build with the SWT version that ships with WSAD 4.03 (which is v1_0_138) without any luck. A few more questions: -do you still see the problem if you close *all* editors and maximize the Console? -what color depth are you running at? (does it fix the problem if you lower it?) -what graphics card/driver are you using?
I was using 32-bit color level. It seems to work ok at 24-bit color level! I can live with that. Thanks for the help! [For future reference, graphics card is ATI XPERT 98 RXL AGP 2X w/ 8 MB. BIOS version is 4.026. Driver is Ati2drad.dll, rel. J5.21.0B18]
Tried running Eclipse with SWT v1_0_138 on WinNT at 1600x1200 and Truecolor (driver doesn't say whether that's 24bit or 32bit) and it works fine. This may be related to the driver.
SSQ, do you have any ideas?
Assuming driver related. The system I tested on actually has a 16m color (24bit) option in addition to the TrueColor option so it's safe to assume that the TrueColor I tested on is 32bit.
