Skip to content

Fix premature deallocation when deallocating with multiple devices. #2867

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.

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

Merged
merged 7 commits into from
May 2, 2020

Conversation

umar456
Copy link
Member

@umar456 umar456 commented May 1, 2020

  • Fix an issue with multiple GPU and memory being freed because the correct device was not active when free was called.
  • Update CLBlast to 1.5.1
  • Set the minimum version for Boost
  • Make sure that the downloaded version of Boost compute is preferred over the system version in case the Boost version is less than 1.7.1
  • Remove old doxygen variable
  • Fix const correctness of the operator* variable

umar456 added 6 commits May 1, 2020 17:14
* Arrays were being freed prematurely because the device associated
  with the array was not active. This change makes sure that we call
  setDevice before the memory is freed so we find the correct pointer
  in the memory manager.
@umar456 umar456 added this to the 3.7.2 milestone May 1, 2020
syurkevi
syurkevi previously approved these changes May 1, 2020
@9prady9 9prady9 merged commit db3a893 into arrayfire:master May 2, 2020
@9prady9 9prady9 deleted the fix_mgpu branch May 2, 2020 06:53
@9prady9 9prady9 restored the fix_mgpu branch May 2, 2020 06:53
@umar456 umar456 deleted the fix_mgpu branch June 26, 2020 18:38
@umar456 umar456 mentioned this pull request Jun 27, 2020
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants