-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Panic in deno 1.46 fmt for large swagger-ui file #28519
Labels
deno fmt
Related to the "deno fmt" subcommand or dprint
Comments
Looks like it's not panicking anymore in the latest version of Deno Error formatting: /Users/marvinhagemeister/dev/test/deno-fmt-foo/main.ts
Formatting not stable. Bailed after 5 tries. This indicates a bug in the formatter where it formats the file differently each time. As a temporary workaround you can ignore this file.
Checked 1 file |
running
the process OOMs
It opened 444 distinct files (syscall
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I ran into a
deno fmt
panic for this file. Reporting as requestedhttps://gist.github.com/rgrannell1/1944f8be41240f7eda221113add195c2
============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.
Platform: linux x86_64
Version: 1.46.3
Args: ["deno", "fmt"]
thread 'tokio-runtime-worker' panicked at cli/tools/fmt.rs:754:11:
Formatting not stable. Bailed after 5 tries. This indicates a bug in the formatter where it formats the file (/home/rg/Code/websites/ui.common-storage.rgrannell.xyz/swagger-ui.js) differently each time. As a temporary workaround you can ignore this file.
stack backtrace:
0: 0x5946e89ff635 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hd736fd5964392270
1: 0x5946e8a3201b - core::fmt::write::hc6043626647b98ea
2: 0x5946e89f969f - std::io::Write::write_fmt::h0d24b3e0473045db
3: 0x5946e89ff40e - std::sys_common::backtrace::print::h45eb8174d25a1e76
4: 0x5946e8a00e79 - std::panicking::default_hook::{{closure}}::haf3f0170eb4f3b53
5: 0x5946e8a00c1a - std::panicking::default_hook::hb5d3b27aa9f6dcda
6: 0x5946e901a7ed - deno::setup_panic_hook::{{closure}}::h33552738c951bb34
7: 0x5946e8a014eb - std::panicking::rust_panic_with_hook::h6b49d59f86ee588c
8: 0x5946e8a01264 - std::panicking::begin_panic_handler::{{closure}}::hd4c2f7ed79b82b70
9: 0x5946e89ffaf9 - std::sys_common::backtrace::__rust_end_short_backtrace::h2946d6d32d7ea1ad
10: 0x5946e8a00f97 - rust_begin_unwind
11: 0x5946e8a2ef33 - core::panicking::panic_fmt::ha02418e5cd774672
12: 0x5946e8c691db - tokio::runtime::task::raw::poll::hbe947dca81b8a0fc
13: 0x5946ead70e70 - std::sys_common::backtrace::__rust_begin_short_backtrace::h441af42626d0a10d
14: 0x5946ead735f2 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h506cb4efabbeeb1b
15: 0x5946e8a0832b - std::sys::pal::unix::thread::Thread::new::thread_start::hb85dbfa54ba503d6
16: 0x7c4142ea1e2e - start_thread
at ./nptl/pthread_create.c:447:8
17: 0x7c4142f33a4c - __GI___clone3
at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
18: 0x0 -
The text was updated successfully, but these errors were encountered: