Opened 8 years ago

Closed 8 years ago

#934 closed defect (invalid)

SIGSEGV http2 close stream

Reported by: nzt4567@… Owned by:
Priority: minor Milestone:
Component: nginx-module Version: 1.9.x
Keywords: segfault, sigsegv, http2, lingering close Cc:
uname -a: Linux <hostname> 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.9.12
built by gcc 4.9.2 (Debian 4.9.2-10)
built with OpenSSL 1.0.2f 28 Jan 2016
TLS SNI support enabled
configure arguments: --with-http_geoip_module --with-http_secure_link_module --with-http_ssl_module --with-http_v2_module

Description

This segfault occurs randomly, mostly shortly after starting nginx. The corefile has more then 14G so please let me know what other values from it you might need. There is no problem in helping you debug this.

Thanks,
Tomas

Attachments (1)

sigsegv_gdb_bt.txt​ (5.1 KB ) - added by nzt4567@… 8 years ago.
BT full trace of core dump

Download all attachments as: .zip

Change History (4)

by nzt4567@…, 8 years ago

Attachment: sigsegv_gdb_bt.txt​ added

BT full trace of core dump

comment:1 by Valentin V. Bartenev, 8 years ago

The line numbers in your backtrace don't match the source code of nginx 1.9.12, moreover it doesn't look like a valid call stack at all.

Are you sure that you are running unpatched version of nginx 1.9.12?

comment:2 by nzt4567@…, 8 years ago

Sure, my bad, sorry for that. Wrong binary, although the patches included have nothing to do with http2 connections I guess I should try to replicate this on vanilla nginx, right :)

I will let you know if this happens at vanilla nginx as well -> close this now please.

Thanks,
Tomas

comment:3 by Valentin V. Bartenev, 8 years ago

Resolution: → invalid
Status: new → closed

Ok.

Note: See TracTickets for help on using tickets.