Project creation/file import fails silently with long project names, no path length validation before hitting Windows path limit
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- cpp
- Domain
- desktop, operating-systems
Research direction
Start by reproducing project creation and file import with the long names described, then trace the project and import paths associated with the logged filesystem failures. Done means validating the resulting Windows path before filesystem operations and presenting a clear, actionable error instead of a silent or low-level failure.
Written by the indexing model from the issue text.
Description
Version and Platform (required):
- Binary Ninja Version: 6.0.10474-dev Ultimate (c9ea4d90)
- Edition: Ultimate
- OS: Windows 11 Pro
- OS Version: 10.0.26200 (Build 26200)
- CPU Architecture: x64 (AMD64 Family 25 Model 97, running under QEMU/Proxmox virtualization)
Bug Description:
Binary Ninja does not validate the resulting file system path length when creating a project with a long project name. This can cause project creation or file import to fail with no clear indication to the user of why:
- If the project name is around 250 characters, project creation itself fails.
- If the project name is around 200 characters, the project is created successfully, but importing a file into the project fails.
The underlying cause may be related to the Windows path length limit (paths exceeding 250 characters generally cause errors on Windows), though this is a guess based on the character counts observed and has not been confirmed.
Steps To Reproduce:
- In Binary Ninja, start creating a new project
- Set the project name to a string approximately 250 characters long
- Attempt to create the project
- Observe that project creation fails (see log output below)
- Repeat with a project name approximately 200 characters long
- Observe that the project is created successfully
- Attempt to import a file into the project
- Observe that the file import fails (see log output below)
Expected Behavior:
Binary Ninja should validate project name/path length before attempting to create the project directory or copy files, and should give the user a clear, actionable error (e.g. "project name too long") rather than failing with a low-level filesystem error, or should otherwise handle long paths without failing.
Relevant log output:
[Default] copy_file: The system cannot find the path specified.: "C:/Users/vector35/Downloads/helloworld_thread.exe", "C:\Users\vector35\Downloads\12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890.bnpr\data\9a\7f3cf5-984d-4d15-9357-a5b2bd5197e6"
[Projects] Failed creating project due to filesystem error: create_directories: The system cannot find the path specified.: "C:\Users\vector35\Downloads\1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890.bnpr\"
[MainWindow] Failed to create project
[MainWindow] Checking for plugin updates...
[Default] copy_file: The system cannot find the path specified.: "C:/Users/vector35/Downloads/helloworld_thread.exe", "C:\Users\vector35\Downloads\12345679801234567980123456798012345679801234567980123456798012345679801234567980123456798012345679801234567980123456798012345679801234567980123456798012345679801234567980123456798012345679801234567980.bnpr\data\34\70bf80-6783-41ed-bdcb-8ad4c9fec4d2"
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 20
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Vector35/binaryninja-api
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Vector35/binaryninja-api#8540 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8446 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8444 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Vector35/binaryninja-api#8441 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Vector35/binaryninja-api#8404 ·
All issues in Vector35/binaryninja-api
Similar issues
-
ai_reviewed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ydb-platform/ydb#53869 · 3 comments ·
-
bug cert blocker needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
project-chip/connectedhomeip#74373 ·
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31035 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
vllm-project/vllm-ascend#17329 ·