This is a long shot, but I've noticed recently that if I enable runjdwp for jdb in JVMs using Guice I get unexplained OOM errors. jstack shows no thread doing anything, and tools such as YourKit can't get any data once it starts.
I don't have a 100% controlled experiment (i.e., same code without guice) but I do have other code without guice in other VMs, and am not seeing this behavior. I'm using fairly complex Guice features such as the svn-tree version of assisted injection, and moderate aop, so it's not entirely unreasonable that there's a bug somewhere in bytecode generation. So, as I said, it's a long shot, but has anyone else seen unexplained OOM errors in a quiescent JVM with remote debugging for JDB, Eclipse, NetBeans, etc. turned on? Ring any bells? Thank you, Leigh. -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
