bootandy/archived-dust
1
0
Fork 0
mirror of https://github.com/bootandy/dust.git synced 2026-06-08 11:29:05 +03:00
Code Issues 21 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #409] Panic when running dust #175

New Issue
Closed
opened 2026-06-08 11:26:00 +03:00 by zhus · 3 comments
zhus commented 2026-06-08 11:26:00 +03:00
Owner
Copy Link
Copy Source

Originally created by @maanaskarwa on GitHub (Jul 3, 2024).
Original GitHub issue: https://github.com/bootandy/dust/issues/409

just installed rust on a server and ran cargo install du-dust. This is the output when running dust:

thread 'main' panicked at ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.1/src/registry.rs:168:10:
The global thread pool has not been initialized.: ThreadPoolBuildError { kind: GlobalPoolAlreadyInitialized }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

System Info:
LSB Version: core-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy

stack backtrace:
0: 0x55839c439462 -
1: 0x55839c36aabb -
2: 0x55839c410f32 -
3: 0x55839c43e739 -
4: 0x55839c43df5e -
5: 0x55839c43f184 -
6: 0x55839c43eaa2 -
7: 0x55839c43e9f9 -
8: 0x55839c43e9e6 -
9: 0x55839c2b39c2 -
10: 0x55839c2b3dd5 -
11: 0x55839c383a4a -
12: 0x55839c2e59b3 -
13: 0x55839c2c1da3 -
14: 0x55839c2f5a80 -
15: 0x55839c2c8803 -
16: 0x55839c2fe591 -
Indexing: . 0 files, 0B ... - 17: 0x7fd0d4f72d90 - __libc_start_call_main
at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
18: 0x7fd0d4f72e40 - __libc_start_main_impl
at ./csu/../csu/libc-start.c:392:3
19: 0x55839c2c05b5 -
20: 0x0 -

Originally created by @maanaskarwa on GitHub (Jul 3, 2024). Original GitHub issue: https://github.com/bootandy/dust/issues/409 just installed rust on a server and ran cargo install du-dust. This is the output when running dust: thread 'main' panicked at ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.1/src/registry.rs:168:10: The global thread pool has not been initialized.: ThreadPoolBuildError { kind: GlobalPoolAlreadyInitialized } note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace System Info: LSB Version: core-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch Distributor ID: Ubuntu Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy stack backtrace: 0: 0x55839c439462 - <unknown> 1: 0x55839c36aabb - <unknown> 2: 0x55839c410f32 - <unknown> 3: 0x55839c43e739 - <unknown> 4: 0x55839c43df5e - <unknown> 5: 0x55839c43f184 - <unknown> 6: 0x55839c43eaa2 - <unknown> 7: 0x55839c43e9f9 - <unknown> 8: 0x55839c43e9e6 - <unknown> 9: 0x55839c2b39c2 - <unknown> 10: 0x55839c2b3dd5 - <unknown> 11: 0x55839c383a4a - <unknown> 12: 0x55839c2e59b3 - <unknown> 13: 0x55839c2c1da3 - <unknown> 14: 0x55839c2f5a80 - <unknown> 15: 0x55839c2c8803 - <unknown> 16: 0x55839c2fe591 - <unknown> Indexing: . 0 files, 0B ... - 17: 0x7fd0d4f72d90 - __libc_start_call_main at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16 18: 0x7fd0d4f72e40 - __libc_start_main_impl at ./csu/../csu/libc-start.c:392:3 19: 0x55839c2c05b5 - <unknown> 20: 0x0 - <unknown>
zhus closed this issue 2026-06-08 11:26:00 +03:00
zhus commented 2026-06-08 11:26:00 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Jul 3, 2024):

Was this a 32 bit server ?

https://github.com/bootandy/dust/blob/master/src/main.rs#L357

<!-- gh-comment-id:2207229747 --> @bootandy commented on GitHub (Jul 3, 2024): Was this a 32 bit server ? https://github.com/bootandy/dust/blob/master/src/main.rs#L357
zhus commented 2026-06-08 11:26:00 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Jul 3, 2024):

maybe try this:
export RAYON_NUM_THREADS=1

https://github.com/bootandy/dust/issues/296

Although we need to fix what is causing this.

<!-- gh-comment-id:2207232131 --> @bootandy commented on GitHub (Jul 3, 2024): maybe try this: export RAYON_NUM_THREADS=1 https://github.com/bootandy/dust/issues/296 Although we need to fix what is causing this.
zhus commented 2026-06-08 11:26:00 +03:00
Author
Owner
Copy Link
Copy Source

@maanaskarwa commented on GitHub (Jul 8, 2024):

The export command fixed it. This is a 64-bit server (getting x86_64 when running arch)

<!-- gh-comment-id:2213055414 --> @maanaskarwa commented on GitHub (Jul 8, 2024): The export command fixed it. This is a 64-bit server (getting x86_64 when running arch)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 windows help wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus (Sergey Zhukov)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bootandy/archived-dust#175
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?