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

No text appears on macOS 10.9.5 with Intel Iris Pro 1536 MB #2

Closed
jdm opened this issue Feb 7, 2017 · 10 comments
Closed

No text appears on macOS 10.9.5 with Intel Iris Pro 1536 MB #2

jdm opened this issue Feb 7, 2017 · 10 comments

Comments

@jdm
Copy link
Member

jdm commented Feb 7, 2017

Using a 2013 macbook, I see a white background when I run `cargo run --example lorem-ipsum /Library/Fonts/Arial.ttf".

@pcwalton
Copy link
Contributor

pcwalton commented Feb 8, 2017

@jdm Can you retry now?

@jdm
Copy link
Member Author

jdm commented Feb 9, 2017

Still blank.

@jdm
Copy link
Member Author

jdm commented Feb 9, 2017

screen shot 2017-02-08 at 7 02 55 pm

@pcwalton
Copy link
Contributor

pcwalton commented Feb 9, 2017

OK, I think I'll need to add some support for dumping the GPU in use.

If you get a chance, could you try downloading gfxCardStatus (http://gfx.io) and setting to "Integrated Only" and "Discrete Only" and trying to see if one of them works?

@jdm
Copy link
Member Author

jdm commented Feb 9, 2017

It works fine now, whether I'm selecting a particular card or using dynamic switching. That's very peculiar.

@pcwalton
Copy link
Contributor

pcwalton commented Feb 9, 2017

Yuck. Sounds like a driver bug.

Perhaps I can detect whether nothing is being output and disable Pathfinder in that case.

@acdha
Copy link

acdha commented Feb 14, 2017

I encountered the same output on 10.12.3 on an iMac with an NVIDIA GeForce GTX 780M 4096 MB.

@clord
Copy link

clord commented Feb 14, 2017

seeing the same with 2014 rMBP, NVIDIA GeForce GT 750M 2048 MB & Intel Iris Pro 1536 MB

certainly on the discrete part (external monitor attached)

@pcwalton
Copy link
Contributor

I've tagged this issue as "classic", as it likely only applies to Pathfinder 1 ("classic Pathfinder"). Once Pathfinder 2 matures, this issue will be closed. Feel free to reopen if it is still an issue with the new version. Thanks!

@pcwalton
Copy link
Contributor

pcwalton commented Oct 7, 2017

This issue affected Pathfinder 1, which is now obsolete. Please feel free to reopen if this is still an issue with Pathfinder 2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants