iced: Another run example error: `cargo run --example tour`

I’m trying to run the example on my Windows 10, but I come across this:

iced> $Env:RUST_BACKTRACE="full"
iced> cargo run --example tour  
    Finished dev [unoptimized + debuginfo] target(s) in 0.63s
     Running `target\debug\examples\tour.exe`
[2019-12-01T05:21:46Z INFO  winit::platform_impl::platform::window] Guessed window DPI factor: 1
error: process didn't exit successfully: `target\debug\examples\tour.exe` (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)

I tried to backtrace the log, But it seems to only print a line of log about DPI factor. How could I log more to locate this issue?

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 1
Comments: 24 (15 by maintainers)

Most upvoted comments

@Abendstolz Yes, wgpu tries to find an integrated device first unless the power preference is set to HighPerformance.

I think this is a good default for a GUI application. However, I understand there may be cases where an application may prefer to default to a powerful device. We could maybe make this configurable in the Settings struct.

hecrj on Dec 6, 2019

I fixed the problem by updating my intel display drivers to the latest version. When I mentioned that I updated drivers before, I only updated my nvidia drivers, because I honestly forgot I even had anything else.

I think the fact that it chooses the intel adapter is troubling, but not at all an urgent priority, because at worst I can disable it.

ejmahler on Dec 2, 2019

With glow, the iced works. Thanks for everyone!

huangjj27 on May 30, 2020

Processer: AMD A10-5750M with Radeon™ HD graphics Graphics: AMD Radeon HD 8650G + AMD Radeon HD 8790M

After some effort searching around the Internet, I found that these graphic cards don’t support vulkan (the newest usable driver is in crimson 16.2.1, while the mininum vulkan supported version is 16.3).

Some facts that may be help

huangjj27 on Feb 14, 2020