Skip to content

commit d6c3b56745798bdd0c7e4920ebb5b4192225c17b cause H264 encoder crash #6

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

Closed
qiushics opened this issue Feb 2, 2018 · 2 comments
Closed

Comments

@qiushics
Copy link

qiushics commented Feb 2, 2018

Pre commit works well. Maybe system memeory allocation method changed?

commit d6c3b56745798bdd0c7e4920ebb5b4192225c17b

MediaSDK issue

@drprajap
Copy link
Contributor

drprajap commented Feb 2, 2018

We changed the way clients handle Gmm context, and current debug points to issue in media initialization path where it uses invalid GmmClientContext handle, causing various failures due to garbage address. This will be addressed soon by media-driver, fix is under testing.

@drprajap
Copy link
Contributor

drprajap commented Feb 8, 2018

Even though this issue should have been fixed by a703ec7362fedede71940929a1a18d9577324173fd6c3b5 , We are reverting gmmlib change due to possible compatibility issue it may cause, if not properly coordinated with client. This will be reworked and new change will be pushed to avoid any other client side impact.

Reverted commit - f7b5da59be9fcb1edc57394703e96ebaf59a39ff

@drprajap drprajap closed this as completed Feb 8, 2018
VPG-SWE-Github pushed a commit that referenced this issue Dec 15, 2020
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

No branches or pull requests

2 participants