Skip to content
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

UPBGE: Prevent mipmapping while setting VideoFFmpeg #411

Closed
wants to merge 1 commit into from

Conversation

youle31
Copy link
Collaborator

@youle31 youle31 commented Mar 3, 2017

up to date with master 03/03/2017

Bug only on Windows.

See comments on old branch (old pull request)

@youle31 youle31 added the bug label Mar 3, 2017
@youle31 youle31 changed the title UPBGE: UPBGE: Prevent mipmapping while setting VideoFFmpeg UPBGE: Prevent mipmapping while setting VideoFFmpeg Mar 4, 2017
panzergame added a commit that referenced this pull request Mar 6, 2017
In IMB_allocFromBuffer a copy of the image data is proceeded with a call to
MEM_dupallocN. But all the MEM_ prefix functions work with memory allocated
with the same function.
This was not the case in Image::init, so the copy failed and the all the
operations later used to mipmap were invalid and raise segmentation faults.

To fix this issue we use MEM_mallocN in Image::init.

Fix issue #411.
@youle31
Copy link
Collaborator Author

youle31 commented Mar 6, 2017

Fixed in 9c5581b

Thanks panzergame 👍 :)

@youle31 youle31 closed this Mar 6, 2017
@youle31 youle31 deleted the ge_videomipmap2 branch March 6, 2017 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant