View Issue Details

IDProjectCategoryView StatusLast Update
0005344NoesisGUIUnitypublic2026-11-20 19:05
ReporterXaron Assigned Tosfernandez  
PrioritynormalSeveritycrash 
Status assignedResolutionopen 
Product Version4.0.1 
Target Version4.0.2 
Summary0005344: Native game crashes
Description

Hi,

We’re seeing a recurring native crash inside Noesis.dll in our game Sea Power (Unity, Windows x64). In about one month it has occurred 135 times for 109 different users, across all of our releases since at least October. We can’t reproduce it locally, but the crash signature is identical in every event, so we believe it’s a single, deterministic code path.

Environment

NoesisGUI Unity package 4.0.1
Unity 6000.0.85f2, Windows x64 (Windows 10 and 11), Direct3D 11
All GPU vendors are affected (NVIDIA, AMD, Intel). Almost all reports come from native Windows; a few come from Proton/Wine.

Exception
EXCEPTION_ACCESS_VIOLATION_READ at address 0xffffffffffffffff, on the main thread.

Context

The call comes from a MonoBehaviour Update/LateUpdate into Noesis, most likely NoesisView’s per-frame update (input/update). Judging by its signature (two int arguments, bool return), the outermost Noesis function might be View::MouseMove, but we couldn’t verify that without symbols.
The crash happens during normal gameplay, typically minutes after a scene/mission was loaded, not during load or unload.
No other thread was executing Noesis code at the time of the crash.
The read from 0xffffffffffffffff suggests a dangling or invalid pointer, possibly an element that was already released while still being traversed.

Attached Files
PlatformAny

Activities

Issue History

Date Modified Username Field Change
2026-11-20 18:35 Xaron New Issue
2026-11-20 18:35 Xaron File Added: seapower_noesis401_crash_minidumps.zip
2026-11-20 19:05 sfernandez Assigned To => sfernandez
2026-11-20 19:05 sfernandez Status new => assigned
2026-11-20 19:05 sfernandez Target Version => 4.0.2