[ https://issues.apache.org/jira/browse/PROTON-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Petr Matousek updated PROTON-893: --------------------------------- 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). was: Calling the session.close() on non-active session causes client seqfault (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). > Calling the session.close() on non-active session causes client seqfault > ------------------------------------------------------------------------ > > Key: PROTON-893 > URL: https://issues.apache.org/jira/browse/PROTON-893 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c, python-binding > Affects Versions: 0.9.1 > Environment: packages: > qpid-proton-c-0.9-3 > qpid-proton-c-devel-0.9-3 > python-qpid-proton-0.9-3 > Reporter: Petr Matousek > Priority: Minor > Attachments: session_close_con.py, session_close_ssn.py, > stacktrace.txt > > > 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). -- This message was sent by Atlassian JIRA (v6.3.4#6332)