On Thu, Jan 31, 2013 at 6:10 AM, Mark Thomas <ma...@apache.org> wrote:
> On 31/01/2013 03:14, Howard W. Smith, Jr. wrote: > > 5. from what I can see, there is an atmosphere thread that is (possibly) > > causing this issue; please see below and let me know if I should open a > > tomcat7.0.35 JIRA/issue or atmosphere issue on atmosphere github, > because I > > want to upload and/or share/provide the heap dump files; i'm assuming > that > > I should 'not' attach the files via email, and it might not be readable > to > > copy/paste the content here; please advise. > > That looks like a problem with the APR/native connector. Was there any > more text (like a full stack trace) in the error message you quote below? > > I can't see any relevant changes between 7.0.34 and 7.0.35 that might > have triggered this. > > Mark > > > # > > # A fatal error has been detected by the Java Runtime Environment: > > # > > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000180005310, > > pid=2396, tid=3724 > > # > > # JRE version: 7.0_11-b21 > > # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode > > windows-amd64 compressed oops) > > # Problematic frame: > > # C [tcnative-1.dll+0x5310] Java_org_apache_tomcat_jni_Socket_send+0xa0 > > # > > # Core dump written. Default location: > > D:\apache-tomcat-7.0.35\bin\hs_err_pid2396.mdmp > > # > > # If you would like to submit a bug report, please visit: > > # http://bugreport.sun.com/bugreport/crash.jsp > > # The crash happened outside the Java Virtual Machine in native code. > > # See problematic frame for where to report the bug. > > # > > > > --------------- T H R E A D --------------- > > > > Current thread (0x0000000014f08000): JavaThread > "Atmosphere-AsyncWrite-60" > > daemon [_thread_in_native, id=3724, > > stack(0x000000001f130000,0x000000001f230000)] > > Please see https://gist.github.com/4680412
