NVidia driver bug??

I could not test it in other platforms yet, so I can’t be sure that is a NVidia driver bug, but it seems that…

Using the method clCreateImage2D inside a thread (I used pthreads, of course) the object generated is not accessible (you can’t call clGetMemObjectInfo, clGetImageInfo, clReleaseMemObject, or whatever), inside or outside the thread, receiving a segmentation fault. But if you have generated the object outside the thread, the object can be accessed from the main process, or from any subprocess that you want.

I reported it here:

https://devtalk.nvidia.com/default/topic/542755/cuda-programming-and-performance/opencl-images-creation-fails-in-parallel-threads

ocland is designed now as a multithreading server, but I simply moved to a serial server (for the planned number of clients I think that this fact will not be a problem).

If someone could confirm this (In NVidia or in other hardware) would be nice!

Advertisements
This entry was posted in Bugs, Development and tagged , , , , , , , , , , , , , . Bookmark the permalink.

One Response to NVidia driver bug??

  1. Pingback: NVidia OpenCL driver bug?? « Jose Luis Cercós Pita

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s