AcademySoftwareFoundation / AcademySoftwareFoundation/OpenImageIO

[BUG] assert_fail is called

Open
#4,388 18 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
2.4k
Forks
698
Avg merge
2d 23h
Merged PRs (30d)
46

Description

I keep getting assert_fail called in my app. I am using vcpkg, version 2.5.14.0

I don't have a complete stack track, just

> OpenImageIO.dll!fmt::v11::detail::assert_fail(const char * file, int line, const char * message) Line 38 C++
OpenImageIO.dll!fmt::v11::detail::fwrite_fully(const void * ptr, unsigned __int64 count, _iobuf * stream) Line 77 C++
[Inline Frame] OpenImageIO.dll!fmt::v11::detail::print(_iobuf *) Line 1707 C++
OpenImageIO.dll!fmt::v11::vprint_buffered(_iobuf * f, fmt::v11::basic_string_view fmt, fmt::v11::basic_format_args args) Line 1714 C++

Should I define FMT_THROW to something, so it will throw vs. crash? It is currently crashing my app.
I do not have a repro case, it occurs every 10 minutes or so in my app.

Windows 11

![image](https://github.com/user-attachments/assets/c20ef082-41ed-4867-81c8-0c9e0c478de9)

Contributor guide

Open the contributing guide

Research direction

Start from the provided stack trace at fmt::v11::detail::assert_fail and fwrite_fully, then review the 18 issue comments for any narrowed cause. Reproduce on Windows 11 with OpenImageIO 2.5.14.0 via vcpkg and capture a complete stack trace; done means the failure has an identified trigger and a verified fix or documented upstream limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.