You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Zhao Yongming (Created) (JIRA)" <ji...@apache.org> on 2012/02/15 08:56:09 UTC

[jira] [Created] (TS-1111) crash in RangeTransform::handle_event

crash in RangeTransform::handle_event
-------------------------------------

                 Key: TS-1111
                 URL: https://issues.apache.org/jira/browse/TS-1111
             Project: Traffic Server
          Issue Type: Bug
            Reporter: Zhao Yongming
            Assignee: weijin


we have some crashing in range requesting processing, it is on our own tree based on 3.0.x, that maybe the root cause of the do_io_close issue, we are still look at how to fix that, feedback is welcome
{code}
#0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
926	      Debug("transform_range", "RangeTransform destroy: %d", m_output_vio ? m_output_vio->ndone : 0);
(gdb) bt
#0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
#1  0x000000000069145f in EThread::process_event (this=0x2aaaab332010, e=0x591d410, calling_code=1) at I_Continuation.h:146
#2  0x0000000000691b8b in EThread::execute (this=0x2aaaab332010) at UnixEThread.cc:218
#3  0x000000000069092e in spawn_thread_internal (a=0x440bfa0) at Thread.cc:88
#4  0x000000359fe0673d in pthread_create@@GLIBC_2.2.5 () from /lib64/libpthread.so.0
#5  0x0000000000000000 in ?? ()
(gdb) p m_output_vio
$1 = (VIO *) 0x2aaed0029fe8
(gdb) p *m_output_vio
Cannot access memory at address 0x2aaed0029fe8
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (TS-1111) crash in RangeTransform::handle_event

Posted by "Brian Geffon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Geffon resolved TS-1111.
------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.5

Backported to 3.0.x in a3d0dfda5bb73056ff421de3829fc67f9254a556
                
> crash in RangeTransform::handle_event
> -------------------------------------
>
>                 Key: TS-1111
>                 URL: https://issues.apache.org/jira/browse/TS-1111
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Zhao Yongming
>            Assignee: Brian Geffon
>              Labels: crash
>             Fix For: 3.0.5, 3.1.3
>
>         Attachments: transform.patch
>
>
> we have some crashing in range requesting processing, it is on our own tree based on 3.0.x, that maybe the root cause of the do_io_close issue, we are still look at how to fix that, feedback is welcome
> {code}
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> 926	      Debug("transform_range", "RangeTransform destroy: %d", m_output_vio ? m_output_vio->ndone : 0);
> (gdb) bt
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> #1  0x000000000069145f in EThread::process_event (this=0x2aaaab332010, e=0x591d410, calling_code=1) at I_Continuation.h:146
> #2  0x0000000000691b8b in EThread::execute (this=0x2aaaab332010) at UnixEThread.cc:218
> #3  0x000000000069092e in spawn_thread_internal (a=0x440bfa0) at Thread.cc:88
> #4  0x000000359fe0673d in pthread_create@@GLIBC_2.2.5 () from /lib64/libpthread.so.0
> #5  0x0000000000000000 in ?? ()
> (gdb) p m_output_vio
> $1 = (VIO *) 0x2aaed0029fe8
> (gdb) p *m_output_vio
> Cannot access memory at address 0x2aaed0029fe8
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (TS-1111) crash in RangeTransform::handle_event

Posted by "Igor Galić (Updated JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Galić updated TS-1111:
---------------------------

    Backport to Version: 3.0.5
    
> crash in RangeTransform::handle_event
> -------------------------------------
>
>                 Key: TS-1111
>                 URL: https://issues.apache.org/jira/browse/TS-1111
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Zhao Yongming
>            Assignee: Zhao Yongming
>              Labels: crash
>             Fix For: 3.1.3
>
>         Attachments: transform.patch
>
>
> we have some crashing in range requesting processing, it is on our own tree based on 3.0.x, that maybe the root cause of the do_io_close issue, we are still look at how to fix that, feedback is welcome
> {code}
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> 926	      Debug("transform_range", "RangeTransform destroy: %d", m_output_vio ? m_output_vio->ndone : 0);
> (gdb) bt
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> #1  0x000000000069145f in EThread::process_event (this=0x2aaaab332010, e=0x591d410, calling_code=1) at I_Continuation.h:146
> #2  0x0000000000691b8b in EThread::execute (this=0x2aaaab332010) at UnixEThread.cc:218
> #3  0x000000000069092e in spawn_thread_internal (a=0x440bfa0) at Thread.cc:88
> #4  0x000000359fe0673d in pthread_create@@GLIBC_2.2.5 () from /lib64/libpthread.so.0
> #5  0x0000000000000000 in ?? ()
> (gdb) p m_output_vio
> $1 = (VIO *) 0x2aaed0029fe8
> (gdb) p *m_output_vio
> Cannot access memory at address 0x2aaed0029fe8
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Reopened] (TS-1111) crash in RangeTransform::handle_event

Posted by "Brian Geffon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Geffon reopened TS-1111:
------------------------------

      Assignee: Brian Geffon  (was: Zhao Yongming)
    
> crash in RangeTransform::handle_event
> -------------------------------------
>
>                 Key: TS-1111
>                 URL: https://issues.apache.org/jira/browse/TS-1111
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Zhao Yongming
>            Assignee: Brian Geffon
>              Labels: crash
>             Fix For: 3.1.3
>
>         Attachments: transform.patch
>
>
> we have some crashing in range requesting processing, it is on our own tree based on 3.0.x, that maybe the root cause of the do_io_close issue, we are still look at how to fix that, feedback is welcome
> {code}
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> 926	      Debug("transform_range", "RangeTransform destroy: %d", m_output_vio ? m_output_vio->ndone : 0);
> (gdb) bt
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> #1  0x000000000069145f in EThread::process_event (this=0x2aaaab332010, e=0x591d410, calling_code=1) at I_Continuation.h:146
> #2  0x0000000000691b8b in EThread::execute (this=0x2aaaab332010) at UnixEThread.cc:218
> #3  0x000000000069092e in spawn_thread_internal (a=0x440bfa0) at Thread.cc:88
> #4  0x000000359fe0673d in pthread_create@@GLIBC_2.2.5 () from /lib64/libpthread.so.0
> #5  0x0000000000000000 in ?? ()
> (gdb) p m_output_vio
> $1 = (VIO *) 0x2aaed0029fe8
> (gdb) p *m_output_vio
> Cannot access memory at address 0x2aaed0029fe8
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (TS-1111) crash in RangeTransform::handle_event

Posted by "Zhao Yongming (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhao Yongming updated TS-1111:
------------------------------

    Fix Version/s:     (was: 3.1.4)
                   3.1.3
    
> crash in RangeTransform::handle_event
> -------------------------------------
>
>                 Key: TS-1111
>                 URL: https://issues.apache.org/jira/browse/TS-1111
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Zhao Yongming
>            Assignee: weijin
>              Labels: crash
>             Fix For: 3.1.3
>
>         Attachments: transform.patch
>
>
> we have some crashing in range requesting processing, it is on our own tree based on 3.0.x, that maybe the root cause of the do_io_close issue, we are still look at how to fix that, feedback is welcome
> {code}
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> 926	      Debug("transform_range", "RangeTransform destroy: %d", m_output_vio ? m_output_vio->ndone : 0);
> (gdb) bt
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> #1  0x000000000069145f in EThread::process_event (this=0x2aaaab332010, e=0x591d410, calling_code=1) at I_Continuation.h:146
> #2  0x0000000000691b8b in EThread::execute (this=0x2aaaab332010) at UnixEThread.cc:218
> #3  0x000000000069092e in spawn_thread_internal (a=0x440bfa0) at Thread.cc:88
> #4  0x000000359fe0673d in pthread_create@@GLIBC_2.2.5 () from /lib64/libpthread.so.0
> #5  0x0000000000000000 in ?? ()
> (gdb) p m_output_vio
> $1 = (VIO *) 0x2aaed0029fe8
> (gdb) p *m_output_vio
> Cannot access memory at address 0x2aaed0029fe8
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (TS-1111) crash in RangeTransform::handle_event

Posted by "Zhao Yongming (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhao Yongming updated TS-1111:
------------------------------

    Attachment: transform.patch

this is a stupid patch for the current issue, it will not prevent all the crashing. taorui(Wei Jin) will submit a cool fix and clear all the do_io_close related crashing. we are testing in our production, so far so good till now.
                
> crash in RangeTransform::handle_event
> -------------------------------------
>
>                 Key: TS-1111
>                 URL: https://issues.apache.org/jira/browse/TS-1111
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Zhao Yongming
>            Assignee: weijin
>              Labels: crash
>             Fix For: 3.1.3
>
>         Attachments: transform.patch
>
>
> we have some crashing in range requesting processing, it is on our own tree based on 3.0.x, that maybe the root cause of the do_io_close issue, we are still look at how to fix that, feedback is welcome
> {code}
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> 926	      Debug("transform_range", "RangeTransform destroy: %d", m_output_vio ? m_output_vio->ndone : 0);
> (gdb) bt
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> #1  0x000000000069145f in EThread::process_event (this=0x2aaaab332010, e=0x591d410, calling_code=1) at I_Continuation.h:146
> #2  0x0000000000691b8b in EThread::execute (this=0x2aaaab332010) at UnixEThread.cc:218
> #3  0x000000000069092e in spawn_thread_internal (a=0x440bfa0) at Thread.cc:88
> #4  0x000000359fe0673d in pthread_create@@GLIBC_2.2.5 () from /lib64/libpthread.so.0
> #5  0x0000000000000000 in ?? ()
> (gdb) p m_output_vio
> $1 = (VIO *) 0x2aaed0029fe8
> (gdb) p *m_output_vio
> Cannot access memory at address 0x2aaed0029fe8
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (TS-1111) crash in RangeTransform::handle_event

Posted by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-1111:
------------------------------

    Fix Version/s: 3.1.3
    
> crash in RangeTransform::handle_event
> -------------------------------------
>
>                 Key: TS-1111
>                 URL: https://issues.apache.org/jira/browse/TS-1111
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Zhao Yongming
>            Assignee: weijin
>              Labels: crash
>             Fix For: 3.1.3
>
>
> we have some crashing in range requesting processing, it is on our own tree based on 3.0.x, that maybe the root cause of the do_io_close issue, we are still look at how to fix that, feedback is welcome
> {code}
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> 926	      Debug("transform_range", "RangeTransform destroy: %d", m_output_vio ? m_output_vio->ndone : 0);
> (gdb) bt
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> #1  0x000000000069145f in EThread::process_event (this=0x2aaaab332010, e=0x591d410, calling_code=1) at I_Continuation.h:146
> #2  0x0000000000691b8b in EThread::execute (this=0x2aaaab332010) at UnixEThread.cc:218
> #3  0x000000000069092e in spawn_thread_internal (a=0x440bfa0) at Thread.cc:88
> #4  0x000000359fe0673d in pthread_create@@GLIBC_2.2.5 () from /lib64/libpthread.so.0
> #5  0x0000000000000000 in ?? ()
> (gdb) p m_output_vio
> $1 = (VIO *) 0x2aaed0029fe8
> (gdb) p *m_output_vio
> Cannot access memory at address 0x2aaed0029fe8
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (TS-1111) crash in RangeTransform::handle_event

Posted by "Zhao Yongming (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhao Yongming resolved TS-1111.
-------------------------------

    Resolution: Fixed
      Assignee: Zhao Yongming  (was: weijin)

git hash 6c4d2b5005cde3aac142b7419cbf37ea4a21f0e5
                
> crash in RangeTransform::handle_event
> -------------------------------------
>
>                 Key: TS-1111
>                 URL: https://issues.apache.org/jira/browse/TS-1111
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Zhao Yongming
>            Assignee: Zhao Yongming
>              Labels: crash
>             Fix For: 3.1.3
>
>         Attachments: transform.patch
>
>
> we have some crashing in range requesting processing, it is on our own tree based on 3.0.x, that maybe the root cause of the do_io_close issue, we are still look at how to fix that, feedback is welcome
> {code}
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> 926	      Debug("transform_range", "RangeTransform destroy: %d", m_output_vio ? m_output_vio->ndone : 0);
> (gdb) bt
> #0  0x00000000004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, event=1, edata=<value optimized out>) at Transform.cc:926
> #1  0x000000000069145f in EThread::process_event (this=0x2aaaab332010, e=0x591d410, calling_code=1) at I_Continuation.h:146
> #2  0x0000000000691b8b in EThread::execute (this=0x2aaaab332010) at UnixEThread.cc:218
> #3  0x000000000069092e in spawn_thread_internal (a=0x440bfa0) at Thread.cc:88
> #4  0x000000359fe0673d in pthread_create@@GLIBC_2.2.5 () from /lib64/libpthread.so.0
> #5  0x0000000000000000 in ?? ()
> (gdb) p m_output_vio
> $1 = (VIO *) 0x2aaed0029fe8
> (gdb) p *m_output_vio
> Cannot access memory at address 0x2aaed0029fe8
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira