Re: [protobuf] Deadlock problems with protobuf static initialization in Java
I think this is http://b/issue?id=2267627 On Sat, May 15, 2010 at 10:02 PM, Igor Gatis igorga...@gmail.com wrote: Agreed. So I guess I need to start looking for the deadlock in my code. Do you know any tool to help me out on that? On Sun, May 16, 2010 at 1:38 AM, Christopher Smith cbsm...@gmail.comwrote: Never seen it before... and the Java code is pretty extensively used. Surely someone would have hit this before. --Chris On May 15, 2010, at 9:03 PM, Igor Gatis igorga...@gmail.com wrote: Have anyone experienced deadlock problems related to Java protobuf generated messages static initialization? My multithreaded app seems to be stuck around internalBuildGeneratedFileFrom method. Workaround so far was to move first reference to one of my generated classes to out side of a synchronized block. I'm wondering whether protobuf initialization is deadlock proof/free. -Gatis -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.comprotobuf%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/protobuf?hl=en. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.comprotobuf%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/protobuf?hl=en. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Deadlock problems with protobuf static initialization in Java
Err. Got my mailing lists mixed up. I think this is due to http://bugs.sun.com/view_bug.do?bug_id=6501158 The suggested workaround has been to force initialization of your classes in main, before threads are spawned. On Sun, May 16, 2010 at 1:18 AM, Jason Hsueh jas...@google.com wrote: I think this is http://b/issue?id=2267627 On Sat, May 15, 2010 at 10:02 PM, Igor Gatis igorga...@gmail.com wrote: Agreed. So I guess I need to start looking for the deadlock in my code. Do you know any tool to help me out on that? On Sun, May 16, 2010 at 1:38 AM, Christopher Smith cbsm...@gmail.comwrote: Never seen it before... and the Java code is pretty extensively used. Surely someone would have hit this before. --Chris On May 15, 2010, at 9:03 PM, Igor Gatis igorga...@gmail.com wrote: Have anyone experienced deadlock problems related to Java protobuf generated messages static initialization? My multithreaded app seems to be stuck around internalBuildGeneratedFileFrom method. Workaround so far was to move first reference to one of my generated classes to out side of a synchronized block. I'm wondering whether protobuf initialization is deadlock proof/free. -Gatis -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.comprotobuf%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/protobuf?hl=en. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.comprotobuf%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/protobuf?hl=en. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Deadlock problems with protobuf static initialization in Java
Never seen it before... and the Java code is pretty extensively used. Surely someone would have hit this before. --Chris On May 15, 2010, at 9:03 PM, Igor Gatis igorga...@gmail.com wrote: Have anyone experienced deadlock problems related to Java protobuf generated messages static initialization? My multithreaded app seems to be stuck around internalBuildGeneratedFileFrom method. Workaround so far was to move first reference to one of my generated classes to out side of a synchronized block. I'm wondering whether protobuf initialization is deadlock proof/free. -Gatis -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Deadlock problems with protobuf static initialization in Java
Agreed. So I guess I need to start looking for the deadlock in my code. Do you know any tool to help me out on that? On Sun, May 16, 2010 at 1:38 AM, Christopher Smith cbsm...@gmail.comwrote: Never seen it before... and the Java code is pretty extensively used. Surely someone would have hit this before. --Chris On May 15, 2010, at 9:03 PM, Igor Gatis igorga...@gmail.com wrote: Have anyone experienced deadlock problems related to Java protobuf generated messages static initialization? My multithreaded app seems to be stuck around internalBuildGeneratedFileFrom method. Workaround so far was to move first reference to one of my generated classes to out side of a synchronized block. I'm wondering whether protobuf initialization is deadlock proof/free. -Gatis -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.comprotobuf%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/protobuf?hl=en. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
