Re: review request (URGENT): 7051206: JSR 292 method name SwitchPoint.isValid is misleading to unwary users; should be hasBeenInvalidated

2011-06-03 Thread Y. Srinivas Ramakrishna
Looks good. Thanks for caring for the unwary user (which i unwittingly represented when i previously pointed out the admittedly somewhat subjective naturalness of the stable negative sense compared with the unstable positive sense). -- ramki On 6/3/2011 12:48 AM, John Rose wrote: > http://cr.open

Re: Possible bug: JVM crash due to GC when using indy

2011-03-28 Thread Y. Srinivas Ramakrishna
On 3/28/2011 1:20 PM, shanka@gmail.com wrote: > On Mon, Mar 28, 2011 at 11:44 AM, Christian Thalinger< > christian.thalin...@oracle.com> wrote: > >> -XX:+UseSerialGC. It seems my previous email didn't make it to the list. >> > > This worked. Well sort of. The JVM doesn't crash because of a GC

Re: Possible bug: JVM crash due to GC when using indy

2011-03-26 Thread Y. Srinivas Ramakrishna
You might try switching on heap verification to see if it finds any issues:- -XX:+UnlockDiagnosticVMOptions -XX:+VerifyBeforeGC -XX:+VerifyafterGC -- ramki On 3/26/2011 8:49 PM, shanka@gmail.com wrote: > Hi All, > > I'm trying to include invoke dynamic in Jython. Currently, I'm just focu

Re: indy and tailc

2010-01-27 Thread Y. Srinivas Ramakrishna
> ... perm gen ... go away. Thanks for all the responses. The bottom line appears to be: please do the needful in the JVM, don't tell me (the user) to size the perm gen explicitly. We'll investigate how we can make that happen. thanks. -- ramki ___ ml

Re: indy and tailc

2010-01-27 Thread Y. Srinivas Ramakrishna
Patrick Wright wrote: ... > > Glad to hear that perm gen will eventually go away. Could you elaborate a little on why it would be nice if the perm gen went away? Where would you like its current contents (which ones, if any, specifically?) to be located and why? thanks! -- ramki

Re: Still crashity crashing

2009-08-04 Thread Y. Srinivas Ramakrishna
So it looks like something is causing the iteration over the oops in an interpreter frame on a Java thread stack to fail, and this happens prior to a GC (so GC is likely not screwing up here, but rather perhaps the interpreter). With those very general remarks, it's over to the MLVM cognoscenti :