search

EmbarkStudios / texture-synthesis

🎨 Example-based texture synthesis written in Rust 🦀
http://embark.rs
Apache License 2.0
1.75k stars 83 forks source link

thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src\libcore\option.rs:1188:5 #144

Closed petsuter closed 3 years ago

petsuter commented 4 years ago

Using texture-synthesis-0.8.0-x86_64-pc-windows-msvc.zip and the provided example images:

C:\texture-synthesis-0.8.0-x86_64-pc-windows-msvc>texture-synthesis.exe --inpaint 1_tile.jpg --out-size 400 --tiling -o out.bmp generate 1.jpg
[00:00:01] ###########################------------- 66%
 stage   6 #############--------------------------- 32%
thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src\libcore\option.rs:1188:5

Sometimes it works, sometimes it doesn't.

biosmanager commented 3 years ago

I have the same problem, in some cases it finishes but often it crashes with this error.

lpil commented 3 years ago

Thanks for the info @biosmanager . Are you also on Windows?

biosmanager commented 3 years ago

Thanks for the info @biosmanager . Are you also on Windows?

Yes.

Jake-Shadle commented 3 years ago

https://github.com/rust-lang/rust/issues/29488 seems like it is likely the same issue you are seeing, but I think there is most likely a different a root cause, as you can see from the output the image generation is not actually finished, so we should not be in shutdown, so having a backtrace would be very helpful to point to what exactly is happening.

If you can install Rust and then clone this repo and do

set RUST_BACKTRACE=1
cd <directory you cloned to>
cargo run --release -- --inpaint imgs/1_tile.jpg --out-size 400 --tiling -o out.bmp generate imgs/1.jpg

that would help us figure out what is going on.

Solido commented 3 years ago

Generation never fail when running from cargo. Replaced the provided release with a fresh build and it is OK So I guess you only need to push a new .exe for windows user Thanks !

Jake-Shadle commented 3 years ago

This should be resolved now in the 0.8.2 release, but please reopen if this is not the case. :slightly_smiling_face: