This repository has been archived by the owner on Aug 28, 2024. It is now read-only.
Issue fixed: dangling pointer that caused by 'UnsafeMutablePointer()' #76
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
husthyc
changed the title
husthyc
changed the title
xta0
reviewed
Nov 11, 2021
xta0
approved these changes
Nov 11, 2021
husthyc
force-pushed
the
master
branch
2 times, most recently
from
0d8774f
to
b83eb59
Compare
…ade invalid model outputs Issue fixed: dangling pointer that 'UnsafeMutablePointer()' casused made invalid model outputs
haib3rl
approved these changes
Jan 18, 2022
MaddyThakker
approved these changes
Jun 24, 2022
|
Any chance this could be merged so I can add a PR to fix the iOS demo app as per this: #83 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolve pytorch/pytorch#66993
Dangling pointer that caused by 'UnsafeMutablePointer()' would make module outputs invalid