Skip to content

[WIP] Fix py::object refcnt bug in RPC return value#37871

Closed
mrshenli wants to merge 4 commits intogh/mrshenli/168/basefrom
gh/mrshenli/168/head
Closed

[WIP] Fix py::object refcnt bug in RPC return value#37871
mrshenli wants to merge 4 commits intogh/mrshenli/168/basefrom
gh/mrshenli/168/head

Conversation

@mrshenli
Copy link
Copy Markdown
Contributor

@mrshenli mrshenli commented May 5, 2020

Stack from ghstack:

jit::toIValue would create a copy of the py::object so we need to
guard it with GIL.

Differential Revision: D21410786

jit::toIValue would create a copy of the py::object so we need to
guard it with GGIL.

fixes #37795
fixes #37765

[ghstack-poisoned]
jit::toIValue would create a copy of the py::object so we need to
guard it with GGIL.

fixes #37795
fixes #37765

Differential Revision: [D21410786](https://our.internmc.facebook.com/intern/diff/D21410786)

[ghstack-poisoned]
mrshenli pushed a commit that referenced this pull request May 5, 2020
jit::toIValue would create a copy of the py::object so we need to
guard it with GGIL.

fixes #37795
fixes #37765

ghstack-source-id: 414e3ca
Pull Request resolved: #37871
@mrshenli mrshenli requested a review from xush6528 May 5, 2020 22:07
@mrshenli
Copy link
Copy Markdown
Contributor Author

mrshenli commented May 5, 2020

This is not sufficient to fix #37795. The error still exist.

jit::toIValue would create a copy of the py::object so we need to
guard it with GIL.

Differential Revision: [D21410786](https://our.internmc.facebook.com/intern/diff/D21410786)

[ghstack-poisoned]
jit::toIValue would create a copy of the py::object so we need to
guard it with GIL.

Differential Revision: [D21410786](https://our.internmc.facebook.com/intern/diff/D21410786)

[ghstack-poisoned]
@mrshenli mrshenli changed the title Fix py::object refcnt bug in RPC return value [WIP] Fix py::object refcnt bug in RPC return value May 6, 2020
mrshenli pushed a commit that referenced this pull request May 6, 2020
jit::toIValue would create a copy of the py::object so we need to
guard it with GIL.

ghstack-source-id: f8d2a97
Pull Request resolved: #37871
@dr-ci
Copy link
Copy Markdown

dr-ci Bot commented May 6, 2020

💊 Build failures summary and remediations

As of commit 4e7d799 (more details on the Dr. CI page):


None of the build failures appear to be your fault 💚



🚧 1 fixed upstream failure:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

Since your merge base is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

Check out the recency history of this "viable master" tracking branch.


This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions on the GitHub issue tracker.

See how this bot performed.

This comment has been revised 2 times.

@mrshenli
Copy link
Copy Markdown
Contributor Author

mrshenli commented May 7, 2020

superseded by #37870

@mrshenli mrshenli closed this May 7, 2020
@facebook-github-bot facebook-github-bot deleted the gh/mrshenli/168/head branch June 7, 2020 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant