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.

Sign up for GitHub

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

Jump to bottom

Pori app gets confused and starts to render seemingly-random images #2096

Closed
jaredhms opened this issue Feb 24, 2017 · 1 comment
Closed

Pori app gets confused and starts to render seemingly-random images #2096

jaredhms opened this issue Feb 24, 2017 · 1 comment
Assignees
@DHowett-MSFT
Labels
Area-Foundation Bug Regression

Comments

@jaredhms
Copy link
Contributor

Navigate around a bit and you'll quickly see various images getting swapped out for others.

image
@jaredhms
Copy link
Contributor Author

This looks like a regression caused by the CG refactor. Thanks, @DHowett-MSFT for help confirming.

Disabling the caching behavior in DisplayTexture.mm (CachedDisplayTextureForImage, etc.) works around the issue.

DHowett-MSFT pushed a commit to DHowett-MSFT/WinObjC that referenced this issue Feb 25, 2017
@DHowett
Reintroduce support for the CGImage destruction listener.
7359e71 
Fixes microsoft#1928.
Fixes microsoft#2096.
Refs microsoft#2098.
@DHowett-MSFT DHowett-MSFT mentioned this issue Feb 25, 2017
Merged
DHowett-MSFT pushed a commit that referenced this issue Feb 27, 2017
@DHowett
Reintroduce support for the CGImage destruction listener. (#2099)
2308749 
Fixes #1928.
Fixes #2096.
Refs #2098.
rajsesh pushed a commit to rajsesh/WinObjC that referenced this issue Mar 1, 2017
@DHowett
Reintroduce support for the CGImage destruction listener. (microsoft#…
a01904f 
…2099)

Fixes microsoft#1928.
Fixes microsoft#2096.
Refs microsoft#2098.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DHowett-MSFT DHowett-MSFT

Labels
Area-Foundation Bug Regression
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jaredhms @DHowett-MSFT @tadam-msft