United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-8010999 : [macosx] a constrain of the top level window should be improved

Details
Type:
Bug
Submit Date:
2013-03-28
Status:
Closed
Updated Date:
2014-07-31
Project Name:
JDK
Resolved Date:
2014-04-16
Component:
client-libs
OS:
os_x
Sub-Component:
java.awt
CPU:
x86
Priority:
P2
Resolution:
Fixed
Affected Versions:
7u4,8
Fixed Versions:
8u20 (b11)

Related Reports
Backport:
Backport:
Duplicate:
Relates:
Relates:

Sub Tasks

Description
7160609 adds the code, which constrain initial size of the window to the size of screen. And this lead to the strange behavior in the applets, when its size is larger than the screen. 
This logic should be improved. The maximum size of the window(and our surface) should be constrained by the maximum size of the opengl texture or CAlayer. Or we should not create windowsurface until native window is constrained by the system. At least it should not depend from the current screen resolution.
                                    

Comments
Not verified
                                     
2014-07-31
URL:   http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/rev/357080a6898d
User:  lana
Date:  2014-04-21 17:37:29 +0000

                                     
2014-04-21
re-opening this record so that it can be used for 8u20
                                     
2014-04-16
URL:   http://hg.openjdk.java.net/jdk8u/jdk8u-dev/jdk/rev/357080a6898d
User:  serb
Date:  2014-04-16 09:36:56 +0000

                                     
2014-04-16
The maximum possible window size is hardcoded in CGLGraphicsConfig.java = 8192
                                     
2014-02-27
This is an Apple bug reproducible on some systems, it was submitted to Apple and got id 15196228

The MAX_TEXTURE_SIZE reported by OpenGL could be very different from the real value. On some systems they differ more than 2 times. In case the texture is too big all OpenGL commands go well and do not report any error, just the texture is not rendered or rendered incorrectly, so there is absolutely no way to detect such situation from the code. Native example suffers from the same issue, so it's not a bug in Java. Firefox suffered from the same issue and they have hard-coded 4096 as a maximum texture size, however this is too little for us. So the current implementation of the max texture size querying look more or less correct. This could be improved only when apple fixes it's bug in OpenGL.
                                     
2013-10-10
please fix it, high appreciated!
                                     
2013-10-03
I disagree with deferring this issue. Incorrect texture size constraints may potentially cause JVM crashes (e.g. see JDK-8023159). This bug needs to be fixed in JDK 8.
                                     
2013-08-20
This is not labeled as 8 defer request candidate so far
                                     
2013-06-17
Example why constrain via screen bounds is a bad idea. JDK-8015100
                                     
2013-05-22
Vivian is looking at this
                                     
2013-04-09



Hardware and Software, Engineered to Work Together