Uploaded image for project: 'Qpid Proton'
  1. Qpid Proton
  2. PROTON-893

Calling session.close() on non-active session causes client segfault

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • proton-0.9.1
    • None
    • python-binding
    • packages:
      qpid-proton-c-0.9-3
      qpid-proton-c-devel-0.9-3
      python-qpid-proton-0.9-3

    Description

      Calling the session.close() on non-active session causes client segfault (see the attached reproducer session_close_con.py).

      Moreover calling connection.session().close() causes client seqfault even if the session shall be in active state (see the attached reproducer session_close_ssn.py).

      Attachments

        1. stacktrace.txt
          12 kB
          Petr Matousek
        2. session_close_ssn.py
          0.5 kB
          Petr Matousek
        3. session_close_con.py
          0.4 kB
          Petr Matousek

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jross Justin Ross
            pematous Petr Matousek

            Dates

              Created:
              Updated:

              Slack

                Issue deployment