Open myrrlyn opened 4 years ago
I am the author of the turtle crate and I can help provide details about any of the rendering code. All of the code dealing with pathfinder is in this file: https://github.com/sunjay/turtle/blob/async/src/renderer_server/renderer.rs
My guess is that this is happening sometime during drop. The turtle crate stops rendering after the drawing is complete, so I don't think it could be in the middle of any draw calls. Happy to try to reduce it if you give me some idea of where to look.
Oh, right:
Closing the window during active draw routines causes the same top-level message about error 0x502, but I do not receive a backtrace.
Retry with my environment forced to RUST_BACKTRACE="full"
gives me two backtraces, though the second appears to be turtle
’s and unrelated to Pathfinder:
Platform
Windows 10 x64, build
19631.mn_release-200514-1410
Steps
Behavior
The program draws a heart on-screen. Wait for the window to be filled with pink, indicating that the program is complete, and idling.
Close the window.
This double-panics. The
turtle
crate begins a panic when its IPC connections are severed, so I am unsure if the overlapping panic is Pathfinder's.Backtrace
The backtrace is quite long:
I am filing this against Pathfinder, as it is mentioned in traces 12-40; specifically, function
pathfinder_gl::ck
appears to panic twiceNotes
This does not happen in
cargo run --example heart --release
. It appears only in development builds, and is not affected by the[profile.dev] opt-level
setting inturtle
’s manifest, nor by switching fromcrates.io
to current Git master.