Opened 8 years ago
Closed 8 years ago
#666 closed defect (fixed)
OpenCL errors on exit
Reported by: | pkienzle | Owned by: | wojciech |
---|---|---|---|
Priority: | minor | Milestone: | SasView 4.1.0 |
Component: | SasView | Keywords: | |
Cc: | Work Package: | SasView Bug Fixing |
Description
$ sascomp barbell INFO:root:building barbell-float32 for OpenCL HD Graphics 4000 OCL32 t=348.29 ms, intensity=266902 INFO:root:building barbell-float64 for OpenCL Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz OCL64 t=275.28 ms, intensity=266902 |OCL32-OCL64| max:1.228e-03 median:4.890e-04 98%:1.143e-03 rms:5.872e-04 zero-offset:+5.058e-04 |(OCL32-OCL64)/OCL64| max:4.591e-07 median:2.552e-07 98%:4.398e-07 rms:2.754e-07 zero-offset:+2.555e-07 Exception AttributeError: "'NoneType' object has no attribute 'clobj__delete'" in <bound method _Program.__del__ of <pyopencl.cffi_cl._Program object at 0x103928590>> ignored Exception AttributeError: "'NoneType' object has no attribute 'clobj__delete'" in <bound method _Program.__del__ of <pyopencl.cffi_cl._Program object at 0x103908b10>> ignored Exception AttributeError: "'NoneType' object has no attribute 'clobj__delete'" in <bound method CommandQueue.__del__ of <pyopencl.cffi_cl.CommandQueue object at 0x1039037d0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'clobj__delete'" in ignored Exception AttributeError: "'NoneType' object has no attribute 'clobj__delete'" in <bound method CommandQueue.__del__ of <pyopencl.cffi_cl.CommandQueue object at 0x103903950>> ignored Exception AttributeError: "'NoneType' object has no attribute 'clobj__delete'" in ignored Exception AttributeError: "'NoneType' object has no attribute 'clobj__delete'" in ignored Exception AttributeError: "'NoneType' object has no attribute 'clobj__delete'" in ignored
Change History (6)
comment:1 Changed 8 years ago by pkienzle
comment:2 Changed 8 years ago by pkienzle
Reported on Debian
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819448
Fails on OS X 10.9.5 with pyopencl 2016.1 and 2015.2.4, but not with 2015.1
comment:3 Changed 8 years ago by pkienzle
Solution may be to hold the version at 2015.1 until a newer version works; document that this should be checked in the package dependency table (we have all the dependencies listed in one and only one place, right?).
comment:4 Changed 8 years ago by wojciech
- Owner set to wojciech
- Status changed from new to assigned
comment:5 Changed 8 years ago by wojciech
Currently we keep requirements in two places: check_packages.py and requirements.txt. I've added requirements for pyopencl 2015.1
comment:6 Changed 8 years ago by wojciech
- Resolution set to fixed
- Status changed from assigned to closed
Note: See
TracTickets for help on using
tickets.
Note: macbook pro OS 10.9.5