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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
numpy-gitbot opened this issue Oct 19, 2012 · 4 comments
Closed

Reference count error, in array_reshape? (Trac #710) #1308

numpy-gitbot opened this issue Oct 19, 2012 · 4 comments
Labels
00 - Bug component: Other
Milestone
1.1.0

Comments

@numpy-gitbot
Copy link

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
@numpy-gitbot
Copy link
Author

@pv wrote on 2008-03-21

Confirm segfault in numpy.test(), for r4899 and r4898 but not for r4885. Further bisection search (using hg bisect, btw) shows that the segfaulting is introduced in r4897.

@numpy-gitbot
Copy link
Author

@pv wrote on 2008-03-21

... also the buildbot confirms, this, see
http://buildbot.scipy.org/builders/Linux_x86_Fedora_Py2.6/builds/244/steps/shell_2/logs/stdio
http://buildbot.scipy.org/builders/Linux_x86_Fedora_Py2.6/builds/243/steps/shell_2/logs/stdio

@numpy-gitbot
Copy link
Author

trac user matthieu.brucher wrote on 2008-03-21

Stéfan reverted the patch in r4905, so the issue should be solved now.

@numpy-gitbot
Copy link
Author

@stefanv wrote on 2008-03-21

My mistake, sorry.

@numpy-gitbot numpy-gitbot mentioned this issue Oct 23, 2012
Closed
@mhvk mhvk mentioned this issue May 16, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
00 - Bug component: Other
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
1 participant
@numpy-gitbot
0