You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "yunfei chen (Created) (JIRA)" <ji...@apache.org> on 2011/12/26 05:50:32 UTC

[jira] [Created] (TS-1063) prefetch resource leak

prefetch  resource leak
-----------------------

                 Key: TS-1063
                 URL: https://issues.apache.org/jira/browse/TS-1063
             Project: Traffic Server
          Issue Type: Bug
          Components: HTTP
    Affects Versions: 3.0.2
         Environment: linux(ubuntu)
            Reporter: yunfei chen


configuration:
 records.config
   CONFIG proxy.config.prefetch.prefetch_enabled INT 1 
   CONFIG proxy.config.prefetch.default_url_proto STRING udp 
   CONFIG proxy.config.prefetch.default_data_proto STRING udp 
 prefetch.config
   prefetch child




[Dec 26 10:07:44.129] Server {2964810608} WARNING: too many connections, throttling
[Dec 26 10:17:44.176] Server {2964810608} WARNING: too many connections, throttling






FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
/usr/local/bin/traffic_server - STACK TRACE: 
FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
/usr/local/bin/traffic_server - STACK TRACE: 
/usr/local/bin/traffic_server - STACK TRACE: 
FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
/usr/local/bin/traffic_server - STACK TRACE: 
FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
/usr/local/bin/traffic_server - STACK TRACE: 
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
  
 


 

#0  0x0012e416 in __kernel_vsyscall ()
#1  0x005c9941 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2  0x005cce42 in abort () at abort.c:92
#3  0x00520055 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#4  0x0051df35 in ?? () from /usr/lib/libstdc++.so.6
#5  0x0051df72 in std::terminate() () from /usr/lib/libstdc++.so.6
#6  0x0051e0e1 in __cxa_throw () from /usr/lib/libstdc++.so.6
#7  0x0051e677 in operator new(unsigned int) () from /usr/lib/libstdc++.so.6
#8  0x0051e74d in operator new[](unsigned int) () from /usr/lib/libstdc++.so.6
#9  0x081488fd in DynArray<char>::resize (this=0x748ff4c, new_size=64) at ../lib/ts/DynArray.h:174
#10 0x0815d5da in DynArray<char>::operator() (this=0x748ff4c, idx=0) at ../lib/ts/DynArray.h:122
#11 0x0815a9bb in HtmlParser::ScanHtmlForURL (this=0x748ff3c, r=0xbabb3ac0, url=0xb70921ec, url_end=0xb70921e8) at Update.cc:1874
#12 0x0815a86a in HtmlParser::ParseHtml (this=0x748ff3c, r=0xbabb3ac0, url=0xb70921ec, url_end=0xb70921e8) at Update.cc:1820
#13 0x08140816 in PrefetchTransform::parse_data (this=0x748fe88, reader=0xbabb3ac0) at Prefetch.cc:543
#14 0x0813ffe8 in PrefetchTransform::handle_event (this=0x748fe88, event=1, edata=0x5991b530) at Prefetch.cc:435
#15 0x08104ba5 in Continuation::handleEvent (this=0x748fe88, event=1, data=0x5991b530)
    at ../iocore/eventsystem/I_Continuation.h:146
#16 0x0830a9f5 in EThread::process_event (this=0xb7497008, e=0x5991b530, calling_code=1) at UnixEThread.cc:140
#17 0x0830ac38 in EThread::execute (this=0xb7497008) at UnixEThread.cc:189
#18 0x0830900e in spawn_thread_internal (a=0x895df28) at Thread.cc:88
#19 0x00165cc9 in start_thread (arg=0xb7092b70) at pthread_create.c:304
#20 0x0066f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130


--
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-1063) prefetch resource leak

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

Leif Hedstrom updated TS-1063:
------------------------------

    Fix Version/s: 3.1.4
    
> prefetch  resource leak
> -----------------------
>
>                 Key: TS-1063
>                 URL: https://issues.apache.org/jira/browse/TS-1063
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>    Affects Versions: 3.0.2
>         Environment: linux(ubuntu)
>            Reporter: yunfei chen
>             Fix For: 3.1.4
>
>
> configuration:
>  records.config
>    CONFIG proxy.config.prefetch.prefetch_enabled INT 1 
>    CONFIG proxy.config.prefetch.default_url_proto STRING udp 
>    CONFIG proxy.config.prefetch.default_data_proto STRING udp 
>  prefetch.config
>    prefetch child
> [Dec 26 10:07:44.129] Server {2964810608} WARNING: too many connections, throttling
> [Dec 26 10:17:44.176] Server {2964810608} WARNING: too many connections, throttling
> FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
> /usr/local/bin/traffic_server - STACK TRACE: 
> FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
> FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
> /usr/local/bin/traffic_server - STACK TRACE: 
> /usr/local/bin/traffic_server - STACK TRACE: 
> FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
> /usr/local/bin/traffic_server - STACK TRACE: 
> FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
> /usr/local/bin/traffic_server - STACK TRACE: 
> terminate called after throwing an instance of 'std::bad_alloc'
>   what():  std::bad_alloc
>   
>  
>  
> #0  0x0012e416 in __kernel_vsyscall ()
> #1  0x005c9941 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
> #2  0x005cce42 in abort () at abort.c:92
> #3  0x00520055 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
> #4  0x0051df35 in ?? () from /usr/lib/libstdc++.so.6
> #5  0x0051df72 in std::terminate() () from /usr/lib/libstdc++.so.6
> #6  0x0051e0e1 in __cxa_throw () from /usr/lib/libstdc++.so.6
> #7  0x0051e677 in operator new(unsigned int) () from /usr/lib/libstdc++.so.6
> #8  0x0051e74d in operator new[](unsigned int) () from /usr/lib/libstdc++.so.6
> #9  0x081488fd in DynArray<char>::resize (this=0x748ff4c, new_size=64) at ../lib/ts/DynArray.h:174
> #10 0x0815d5da in DynArray<char>::operator() (this=0x748ff4c, idx=0) at ../lib/ts/DynArray.h:122
> #11 0x0815a9bb in HtmlParser::ScanHtmlForURL (this=0x748ff3c, r=0xbabb3ac0, url=0xb70921ec, url_end=0xb70921e8) at Update.cc:1874
> #12 0x0815a86a in HtmlParser::ParseHtml (this=0x748ff3c, r=0xbabb3ac0, url=0xb70921ec, url_end=0xb70921e8) at Update.cc:1820
> #13 0x08140816 in PrefetchTransform::parse_data (this=0x748fe88, reader=0xbabb3ac0) at Prefetch.cc:543
> #14 0x0813ffe8 in PrefetchTransform::handle_event (this=0x748fe88, event=1, edata=0x5991b530) at Prefetch.cc:435
> #15 0x08104ba5 in Continuation::handleEvent (this=0x748fe88, event=1, data=0x5991b530)
>     at ../iocore/eventsystem/I_Continuation.h:146
> #16 0x0830a9f5 in EThread::process_event (this=0xb7497008, e=0x5991b530, calling_code=1) at UnixEThread.cc:140
> #17 0x0830ac38 in EThread::execute (this=0xb7497008) at UnixEThread.cc:189
> #18 0x0830900e in spawn_thread_internal (a=0x895df28) at Thread.cc:88
> #19 0x00165cc9 in start_thread (arg=0xb7092b70) at pthread_create.c:304
> #20 0x0066f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

--
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-1063) prefetch resource leak

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

Leif Hedstrom updated TS-1063:
------------------------------

    Fix Version/s:     (was: 3.1.6)
                   3.3.0

Moving out to v3.3.0, move back to 3.1.4 if this will be work on *soon*.
                
> prefetch  resource leak
> -----------------------
>
>                 Key: TS-1063
>                 URL: https://issues.apache.org/jira/browse/TS-1063
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>    Affects Versions: 3.0.2
>         Environment: linux(ubuntu)
>            Reporter: yunfei chen
>             Fix For: 3.3.0
>
>
> configuration:
>  records.config
>    CONFIG proxy.config.prefetch.prefetch_enabled INT 1 
>    CONFIG proxy.config.prefetch.default_url_proto STRING udp 
>    CONFIG proxy.config.prefetch.default_data_proto STRING udp 
>  prefetch.config
>    prefetch child
> [Dec 26 10:07:44.129] Server {2964810608} WARNING: too many connections, throttling
> [Dec 26 10:17:44.176] Server {2964810608} WARNING: too many connections, throttling
> FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
> /usr/local/bin/traffic_server - STACK TRACE: 
> FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
> FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
> /usr/local/bin/traffic_server - STACK TRACE: 
> /usr/local/bin/traffic_server - STACK TRACE: 
> FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
> /usr/local/bin/traffic_server - STACK TRACE: 
> FATAL: ink_memalign: couldn't allocate 524288 bytes at alignment 4096 - insufficient memory
> /usr/local/bin/traffic_server - STACK TRACE: 
> terminate called after throwing an instance of 'std::bad_alloc'
>   what():  std::bad_alloc
>   
>  
>  
> #0  0x0012e416 in __kernel_vsyscall ()
> #1  0x005c9941 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
> #2  0x005cce42 in abort () at abort.c:92
> #3  0x00520055 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
> #4  0x0051df35 in ?? () from /usr/lib/libstdc++.so.6
> #5  0x0051df72 in std::terminate() () from /usr/lib/libstdc++.so.6
> #6  0x0051e0e1 in __cxa_throw () from /usr/lib/libstdc++.so.6
> #7  0x0051e677 in operator new(unsigned int) () from /usr/lib/libstdc++.so.6
> #8  0x0051e74d in operator new[](unsigned int) () from /usr/lib/libstdc++.so.6
> #9  0x081488fd in DynArray<char>::resize (this=0x748ff4c, new_size=64) at ../lib/ts/DynArray.h:174
> #10 0x0815d5da in DynArray<char>::operator() (this=0x748ff4c, idx=0) at ../lib/ts/DynArray.h:122
> #11 0x0815a9bb in HtmlParser::ScanHtmlForURL (this=0x748ff3c, r=0xbabb3ac0, url=0xb70921ec, url_end=0xb70921e8) at Update.cc:1874
> #12 0x0815a86a in HtmlParser::ParseHtml (this=0x748ff3c, r=0xbabb3ac0, url=0xb70921ec, url_end=0xb70921e8) at Update.cc:1820
> #13 0x08140816 in PrefetchTransform::parse_data (this=0x748fe88, reader=0xbabb3ac0) at Prefetch.cc:543
> #14 0x0813ffe8 in PrefetchTransform::handle_event (this=0x748fe88, event=1, edata=0x5991b530) at Prefetch.cc:435
> #15 0x08104ba5 in Continuation::handleEvent (this=0x748fe88, event=1, data=0x5991b530)
>     at ../iocore/eventsystem/I_Continuation.h:146
> #16 0x0830a9f5 in EThread::process_event (this=0xb7497008, e=0x5991b530, calling_code=1) at UnixEThread.cc:140
> #17 0x0830ac38 in EThread::execute (this=0xb7497008) at UnixEThread.cc:189
> #18 0x0830900e in spawn_thread_internal (a=0x895df28) at Thread.cc:88
> #19 0x00165cc9 in start_thread (arg=0xb7092b70) at pthread_create.c:304
> #20 0x0066f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

--
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