8000 Reference count error, in array_reshape? (Trac #710) · Issue #1308 · numpy/numpy · GitHub
[go: up one dir, main page]

Skip to content
Reference count error, in array_reshape? (Trac #710) #1308
Closed
@numpy-gitbot

Description

@numpy-gitbot

Original ticket http://projects.scipy.org/numpy/ticket/710 on 2008-03-21 by @matthew-brett, assigned to unknown.

In some runs of numpy.test()

*** Reference count error detected:
an attempt was made to deallocate 17 (O) ***
*** Reference count error detected:
an attempt was made to deallocate 17 (O) ***
*** Reference count error detected:
an attempt was made to deallocate 17 (O) ***
(etc)

In [2]: numpy.version
Out[2]: '1.0.5.dev4899'

Linux localhost 2.6.25-rc6_x61 #1 SMP Tue Mar 18 18:22:11 CET 2008 x86_64 Intel(R) Core(TM)2 Duo CPU L7300 @ 1.40GHz GNU/Linux

Valgrind session excerpt:

Ticket #658==26607==
==26607== Conditional jump or move depends on uninitialised value(s)
==26607== at 0x659D56A: PyArray_UpdateFlags (arrayobject.c:5043)
==26607== by 0x65CBC54: PyArray_Newshape (multiarraymodule.c:742)
==26607== by 0x65CC2A3: array_reshape (arraymethods.c:87)
==26607== by 0x51D626D: PyEval_EvalFrameEx (in /usr/lib64/libpython2.5.so.1.0)
==26607== by 0x51D83F7: PyEval_EvalCodeEx (in /usr/lib64/libpython2.5.so.1.0)
==26607== by 0x51D67CC: PyEval_EvalFrameEx (in /usr/lib64/libpython2.5.so.1.0)
==26607== by 0x51D83F7: PyEval_EvalCodeEx (in /usr/lib64/libpython2.5.so.1.0)
==26607== by 0x517F780: (within /usr/lib64/libpython2.5.so.1.0)
==26607== by 0x51633C2: PyObject_Call (in /usr/lib64/libpython2.5.so.1.0)
==26607== by 0x51D504A: PyEval_EvalFrameEx (in /usr/lib64/libpython2.5.so.1.0)
... ok

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0