From mr at sun.com Thu Apr 30 14:43:37 2009 From: mr at sun.com (Mark Reinhold) Date: Thu, 30 Apr 2009 14:43:37 -0700 Subject: M3 stabilization requests for 2009/4/30 Message-ID: <20090430214337.E8A8B5CE0@eggemoggin.niobe.net> Today we have: 6762511 anthony.petrov Translucency is not working on Linux using Metacity 6794764 artem.ananiev Translucent windows are completely repainted on every paint event, on Windows 6812298 anthony.petrov Dynamic GraphicsConfig changes don't work on X11 platforms These first three are nontrivial changes, and none seems critical for M3. Phil, Vita -- what say you? 6834177 vladimir.kozlov Running jsynprog on Solaris Nevada can cause JVM crash VM crash on 64-bit sparc. The fix isn't trivial but it's smaller than it looks, and VM crashes are bad. I'm leaning toward accepting it. Paul? Vita? 6834246 alan.bateman (ch) AsynchronousSocketChannel#write completes with wrong number of bytes written under load (win) Not critical for M3 but the fix is limited to the Windows asynchronous socket-channel code, so if it's wrong then that's the only thing that would break. I'd say "yes" to this one. - Mark From Paul.Hohensee at Sun.COM Thu Apr 30 15:20:07 2009 From: Paul.Hohensee at Sun.COM (Paul Hohensee) Date: Thu, 30 Apr 2009 18:20:07 -0400 Subject: M3 stabilization requests for 2009/4/30 In-Reply-To: <20090430214337.E8A8B5CE0@eggemoggin.niobe.net> References: <20090430214337.E8A8B5CE0@eggemoggin.niobe.net> Message-ID: <49FA2417.9060203@sun.com> The fix is actually more trivial than it looks. Most of the change is just moving source code slightly so that native code gets generated into the code cache rather than into a C++ static byte array. I'd like it accepted. Paul Mark Reinhold wrote: > Today we have: > > 6762511 anthony.petrov Translucency is not working on Linux using > Metacity > > 6794764 artem.ananiev Translucent windows are completely repainted > on every paint event, on Windows > > 6812298 anthony.petrov Dynamic GraphicsConfig changes don't work on > X11 platforms > > These first three are nontrivial changes, and none seems critical for M3. > Phil, Vita -- what say you? > > 6834177 vladimir.kozlov Running jsynprog on Solaris Nevada can cause > JVM crash > > VM crash on 64-bit sparc. The fix isn't trivial but it's smaller than > it looks, and VM crashes are bad. I'm leaning toward accepting it. > Paul? Vita? > > 6834246 alan.bateman (ch) AsynchronousSocketChannel#write > completes with wrong number of bytes written > under load (win) > > Not critical for M3 but the fix is limited to the Windows asynchronous > socket-channel code, so if it's wrong then that's the only thing that > would break. I'd say "yes" to this one. > > - Mark > From vita.santrucek at sun.com Thu Apr 30 15:22:21 2009 From: vita.santrucek at sun.com (Vita Santrucek) Date: Thu, 30 Apr 2009 15:22:21 -0700 (PDT) Subject: M3 stabilization requests for 2009/4/30 In-Reply-To: <20090430214337.E8A8B5CE0@eggemoggin.niobe.net> References: <20090430214337.E8A8B5CE0@eggemoggin.niobe.net> Message-ID: -> 6762511 anthony.petrov Translucency is not working on Linux using -> Metacity Already present in 6u14 for the past 4 weeks, no regressions found so far. I'd be OK to let this one in -> 6794764 artem.ananiev Translucent windows are completely repainted -> on every paint event, on Windows Webrev's not there, but doesn't sound like simple fix. I'd prefer to get this in one in M4. -> 6812298 anthony.petrov Dynamic GraphicsConfig changes don't work on -> X11 platforms Phil, if you consider this one super safe and unlikely to cause regressions I'd take it in, Marina is the Linux/OpenSolaris release and these bugs seem to significantly impact these platforms. If we could get it in b58 it would be better. ->These first three are nontrivial changes, and none seems critical for M3. ->Phil, Vita -- what say you? -> -> 6834177 vladimir.kozlov Running jsynprog on Solaris Nevada can cause -> JVM crash Agreed, we'll have the initial OpenSolaris release on Sparc in early June. I rather makes me wonder if we wouldn't want this fix in 6u14 also. ->VM crash on 64-bit sparc. The fix isn't trivial but it's smaller than ->it looks, and VM crashes are bad. I'm leaning toward accepting it. ->Paul? Vita? -> -> 6834246 alan.bateman (ch) AsynchronousSocketChannel#write -> completes with wrong number of bytes written -> under load (win) -> ->Not critical for M3 but the fix is limited to the Windows asynchronous ->socket-channel code, so if it's wrong then that's the only thing that ->would break. I'd say "yes" to this one. GO. Vita -> ->- Mark -> From Phil.Race at Sun.COM Thu Apr 30 15:35:56 2009 From: Phil.Race at Sun.COM (Phil Race) Date: Thu, 30 Apr 2009 15:35:56 -0700 Subject: M3 stabilization requests for 2009/4/30 In-Reply-To: References: <20090430214337.E8A8B5CE0@eggemoggin.niobe.net> Message-ID: <49FA27CC.9040101@sun.com> Vita Santrucek wrote: > -> 6762511 anthony.petrov Translucency is not working on Linux using > -> Metacity > > Already present in 6u14 for the past 4 weeks, no regressions found so far. > I'd be OK to let this one i I agree. Its in 6u14 as of b04 so I think we can allow it here. > > -> 6794764 artem.ananiev Translucent windows are completely repainted > -> on every paint event, on Windows > > Webrev's not there, but doesn't sound like simple fix. I'd prefer to get > this in one in M4. I see the webrev : http://sa.sfbay.sun.com/projects/awt_data/7/6794764/ I agree, this is a performance fix that so far as I can tell isn't critical to M3 and touches sensitive areas like the Swing repaint manager. > > -> 6812298 anthony.petrov Dynamic GraphicsConfig changes don't work on > -> X11 platforms > > Phil, if you consider this one super safe and unlikely to cause > regressions I'd take it in, Marina is the Linux/OpenSolaris release and > these bugs seem to significantly impact these platforms. > I don't know if I go so far as to call it super-safe. > If we could get it in b58 it would be better. Too late for b58. I guess this is a no unless there's a better justification for the risk and more explanation of the impact. > > ->These first three are nontrivial changes, and none seems critical for M3. > ->Phil, Vita -- what say you? > -> > -> 6834177 vladimir.kozlov Running jsynprog on Solaris Nevada can cause > -> JVM crash > > > Agreed, we'll have the initial OpenSolaris release on Sparc in early June. > I rather makes me wonder if we wouldn't want this fix in 6u14 also. > > OK from me. > ->VM crash on 64-bit sparc. The fix isn't trivial but it's smaller than > ->it looks, and VM crashes are bad. I'm leaning toward accepting it. > ->Paul? Vita? > -> > -> 6834246 alan.bateman (ch) AsynchronousSocketChannel#write > -> completes with wrong number of bytes written > -> under load (win) > -> > ->Not critical for M3 but the fix is limited to the Windows asynchronous > ->socket-channel code, so if it's wrong then that's the only thing that > ->would break. I'd say "yes" to this one. > OK from me. -phil. > > GO. > > Vita > > > -> > ->- Mark > ->