Skip to content

Segfault with http2 with bad connection #2688

Closed
@ThomasObenaus

Description

@ThomasObenaus

I did this

Application that communicates using http2 (nghttp2) with our backend.
In case the connection is bad (mobile phone with edge/gsm) the application crashes each time with a segfault and the same back-trace.

Precondition

  • Bad connection (low bandwidth) with over mobile phone whose datavolume is empty (fallback to 2G).
  • No connection to the internet (firewall closed).
  • Application starts requesting (to reproduce the problem) a lot of requests.
  • dnsmask already complains about too many requests in parallel (max of 150 reached).
  • Opening the fire wall.
  • Waiting for ~1 min --> segfault.

Curl errors

  • When FW is closed: "Cloud not connect"
  • When FW is open: "Timeout reached"

I expected the following

no segfault

curl/libcurl version

Tested with 7.54.0 and 7.60

Libs

nghttp2 1.17.0
c-ares 1.13.9

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions