use wry::WebViewBuilder;

fn main() {
    // ... create window ...

    let webview = WebViewBuilder::new()
        .with_custom_protocol("app".into(), |_webview_id, request, responder| {
            // Simulate async response (e.g., via tokio::spawn)
            std::thread::spawn(move || {
                let response = http::Response::builder()
                    .status(200)
                    .body(std::borrow::Cow::from("hello".as_bytes()))
                    .unwrap();
                responder.respond(response);
            });
        })
        .with_url("app://localhost/index.html")
        .build(&window)
        .unwrap();

    // Drop webview shortly after — on macOS 11, this triggers the crash
    // in stop_task during WKWebView dealloc
    drop(webview);
}

Note: The crash is timing-dependent and more likely when async responses are pending during webview destruction.

**Expected behavior**
Dropping the WebView should not crash. The stop_task callback should safely handle the case where WebKit passes freed pointers during
 dealloc on macOS 11.


**Screenshots**
None

**Platform and Versions (please complete the following information):**
- OS: macOS 11.7.10 (Big Sur)
- Rustc: 1.88
- wry: 0.51 and 0.48


**Additional context**
Proposed fix:

  _this: &ProtocolObject<dyn WKURLSchemeHandler>,
  _sel: objc2::runtime::Sel,
  _webview: *mut AnyObject,  // raw pointer — no implicit objc_retain
  _task: *mut AnyObject,     // raw pointer — no implicit objc_retain
) {
  // no-op: avoid accessing task/webview — macOS 11 may pass freed pointers here
}

2. Enforce explicit drop ordering in the async response handler:

// webview must drop before task: if webview drop triggers dealloc →
// stopAllTasksForPage → platformStopTask, the task must still be alive.
drop(webview);
drop(task);
result