activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Martens (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-199) Segmentation fault at decaf/net/SocketInputStream.cpp (line 108)
Date Thu, 13 Nov 2008 11:32:05 GMT

    [ https://issues.apache.org/activemq/browse/AMQCPP-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47346#action_47346
] 

Alexander Martens commented on AMQCPP-199:
------------------------------------------

Nice to read from you again, Albert!

In my current test, I've reduced the number of runs down to 50, taken out all stomp tests
and I'm restarting the server every time "stresstests.py" exits.
With "top" I can see how the virtual memory assigned to java grows (it doesn't shrink until
server restart) and looks like every new test is speeding this memory consumption up.
Is it possible that the way the client is closing down, causes a memory leak on the server?

Specifically, the "fast" part of the test - between test_Connection (test_openwire_sync.test_openwire_sync)
and  test_version (test_types.test_pyactivemq), seems to be the most memory eating. I don't
remember this behavior with apr (trunk), but I could have simply missed it.

This might not be related to the segmentation fault, but still concerning.


> Segmentation fault at decaf/net/SocketInputStream.cpp (line 108)
> ----------------------------------------------------------------
>
>                 Key: AMQCPP-199
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-199
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Decaf, Openwire
>    Affects Versions: 2.2.1
>         Environment: RHEL 5.2 (32 bits), apr-1.3.3, apr-util-1.3.4, ActiveMQ 5.1, gcc
4.1.2-42 (20071124), Java(TM) SE Runtime Environment (build 1.6.0_06-b02), pyactivemq-0.1.0rc1
>            Reporter: Alexander Martens
>            Assignee: Timothy Bish
>             Fix For: 2.2.2
>
>         Attachments: python.stress.log.gz, stress-again.tar.gz, stress-fc8.log.gz, stress-segfault-1.log.bz2,
stress.out
>
>
> We're getting occasional segmentation faults in our Python based application.
> The easiest way to reproduce it is by running pyactivemq's stress tests (src/tests/stresstest.py).
> The offending line seems to be always the same.
> I send you attached a full gdb postmortem back-trace.
> Any help will be appreciated!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message