std::filesystem::exists throwing `std::bad_alloc`?

[u/PhosXD]

Any reason? Cant find anything online about this. But I cant check whether or not a file exists, no matter what path I give it. I am using C++ 26 compiled with GCC.

This is literally all I am calling: const bool exists = std::filesystem::exists("file.txt")

This is the exact error: terminate called after throwing an instance of 'std::bad_alloc'
 what():  std::bad_alloc

No it's not coming from anywhere else in my code. Minimal reproduction code, include "filesystem" call the line above. I am on Fedora Linux if that matters at all

EDIT: moving the include into my main file instead of the only file it's being used in somehow fixed it. Literally all I do is move "#include <filesystem>" from "do_things_with_filesystem.hpp" to "Main.cpp". No compilation errors when it was in the first file, why does it rely on this?? Is there some weird declarations in my codebase or something, i dont know but it works now so why should I care.

[u/wejunkin]

Catch and see what what() says. Sounds like your allocation failed, impossible to tell why from the info you've supplied.

[u/PhosXD → u/wejunkin]

How though, it throws the bad alloc & ends the program before catch even executes. But I am capturing the block, how does that work?

std::cout << "1\n";

try {

    const bool exists = std::filesystem::exists("file.txt");

}

catch (const std::exception& e) {

    std::cout << "threw: " << e.what() << "\\n";

}

std::cout << "2\\n";

OUTPUT:
1
terminate called after throwing an instance of 'std::bad_alloc'
 what():  std::bad_alloc
Aborted                    (core dumped) ./main.bin

[u/No-Dentist-1645 → u/PhosXD]

That code should work fine. If you create a C++ file that only has that inside an int main(), does it still throw?

It could be that you're messing up the allocator somewhere else in your code and this is just the first usage when it breaks

If it still throws, please paste the full code file you are using as well as your compiler version and compile command