Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#119 zopyx.txng3.ext causes guppy/heapy to segfault

closed-wont-fix
nobody
None
2
2011-11-25
2010-07-30
Ross Patterson
No

> On 7/27/10 2:52 PM, Ross Patterson wrote:
>> I'm trying to do some memory profiling on a Plone 3.3.5 site using heapy
>> from guppy 0.1.9. I've also tried guppy SVN trunk and several older
>> versions all the way back to 0.1. In all cases I'm getting a
>> "Segmentation Fault":
>>
>> >>> from guppy import hpy
>> >>> hp=hpy()
>> >>> hp.heap()
>> Segmentation fault
>>
>> I tried this under two different deployments on different machines with
>> the same results.
>>
>> Has anyone had any luck getting guppy/heapy working under Plone 3? Are
>> there any other good options for profiling memory consumption?
>>
> I didn't have any trouble when I tried guppy, aside from it being
> somewhat slow dealing with such a large heap, and a bit tricky to figure
> out how to use. Powerful, though.

I tracked it down to TextIndexNG3, specifically, removing
zopyx.txng3.ext from sys.path resolved the segfault. So txng3 seems to
conflict with heapy for future reference.

Discussion

  • Andreas Jung
    Andreas Jung
    2011-11-25

    Does not affect the real functionality of TXNG3 in production.

     
  • Andreas Jung
    Andreas Jung
    2011-11-25

    • priority: 5 --> 2
    • status: open --> closed-wont-fix