Avbin load crashes with scipy subpackages

[GoogleCodeExporter]

What steps will reproduce the problem?
1.import scipy.stats 
2.import ctypes
3.lib=ctypes.cdll.LoadLibrary(r"c:\WINDOWS\system32\avbin.dll")

Traceback:
---------------------------------------------------------------------------
WindowsError                              Traceback (most recent call last)

c:\Python25\Lib\site-packages\pyglet\<ipython console> in <module>()

C:\Python25\lib\ctypes\__init__.pyc in LoadLibrary(self, name)
    421
    422     def LoadLibrary(self, name):
--> 423         return self._dlltype(name)
    424
    425 cdll = LibraryLoader(CDLL)

C:\Python25\lib\ctypes\__init__.pyc in __init__(self, name, mode, handle)
    338         self._name = name
    339         if handle is None:
--> 340             self._handle = _dlopen(self._name, mode)
    341         else:
    342             self._handle = handle

WindowsError: [Error 998] Invalid access to memory location 

Environment:
win32 platform (xp), pyglet 1.1.4 with Python 2.5.1 / 2.6.2, scipy version 
0.9.0 / 0.10.0.

Original issue reported on code.google.com by joz...@gmail.com on 14 Dec 2011 at 9:47

• Merged into: #518

[GoogleCodeExporter]

Actually the issue came from an avi file load with pyglet.media:

1 import scipy.stats
2 import pyglet
3
4 source = pyglet.media.load(<avi-file-path>) 

Original comment by joz...@gmail.com on 14 Dec 2011 at 9:56

[GoogleCodeExporter]

streams.pyd and mio_utils.pyd cause the same problem.

import scipy.io.matlab.mio5_utils
import ctypes
ctypes.cdll.LoadLibrary('avbin')

import scipy.io.matlab.streams
import ctypes
ctypes.cdll.LoadLibrary('avbin')

Original comment by Gergo.Ny...@gmail.com on 14 Jun 2012 at 12:04

[GoogleCodeExporter]

Not a problem on linux as far as I can tell. Can somebody check whether this is 
still a problem under 1.2alpha or trunk please?

Original comment by Adam.JT...@gmail.com on 11 Dec 2012 at 11:35

• Changed state: Blocked
• Added labels: OpSys-Windows

[GoogleCodeExporter]

Just noticed that this seems to be the same problem as issue 518. Please try 
the work around given there.

Original comment by Adam.JT...@gmail.com on 11 Dec 2012 at 11:40

• Changed state: Duplicate