IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
112 stars 3 forks source link

The game I made myself crashing if using 1.3+ gb physical memory. #727

Open Denizeri24 opened 3 months ago

Denizeri24 commented 3 months ago

Checklist [README]

Application [Required]

The game I made myself

Processor / Processor Number [Required]

8700K

Graphic Card [Required]

A770 16GB

GPU Driver Version [Required]

31.0.101.5194

Other GPU Driver version

No response

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

scanoutput.txt

Description and steps to reproduce [Required]

Just playing normally, and my game crashing at 1.3+ gb memory usage. Nvidia and AMD gpus dont have this problem..

some notes;

game is X64, compiling with debug mode (no optimizations). dxvk not solving this problem. Also when I use Arc A770, I have to turn off ASLR (my game crashing instantly caused by a770 (again))

Device / Platform

Windows PC (Not laptop)

Crash dumps [Required, if applicable]

No response

Application / Windows logs

Exception Type: 0xc0000005

Rax: 0x18446744071569658384 Rbx: 0x87909192 Rcx: 0x18446744071569658384 Rdx: 0x09311739 Rsi: 0x99295736 Rdi: 0x00000001 Rbp: 0x99398623 Rsp: 0x01357840

| 140807720 | [NONAME]-[wndMgrHide] --> 576 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d4ffc0 | [NONAME]-[PyEval_EvalCodeEx] --> 3608 | 140e19930 | [NONAME]-[function_call] --> 523 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140de5340 | [NONAME]-[instancemethod_call] --> 2600 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d4ffc0 | [NONAME]-[PyEval_EvalCodeEx] --> 3608 | 140e19930 | [NONAME]-[function_call] --> 523 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140de5340 | [NONAME]-[instancemethod_call] --> 2600 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140d9a4d0 | [NONAME]-[slot_tp_init] --> 5870 | 140da8300 | [NONAME]-[type_call] --> 763 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d4ffc0 | [NONAME]-[PyEval_EvalCodeEx] --> 3608 | 140e19930 | [NONAME]-[function_call] --> 523 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140de5340 | [NONAME]-[instancemethod_call] --> 2600 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140d9a4d0 | [NONAME]-[slot_tp_init] --> 5870 | 140da8300 | [NONAME]-[type_call] --> 763 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d4ffc0 | [NONAME]-[PyEval_EvalCodeEx] --> 3608 | 140e19930 | [NONAME]-[function_call] --> 523 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140de5340 | [NONAME]-[instancemethod_call] --> 2600 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140d9a4d0 | [NONAME]-[slot_tp_init] --> 5870 | 140da8300 | [NONAME]-[type_call] --> 763 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d4ffc0 | [NONAME]-[PyEval_EvalCodeEx] --> 3608 | 140e19930 | [NONAME]-[function_call] --> 523 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140de5340 | [NONAME]-[instancemethod_call] --> 2600 | 140d283c0 | [NONAME]-[PyObject_Call] --> 2545 | 140d4f090 | [NONAME]-[PyEval_CallObjectWithKeywords] --> 4246 | 140ae93b0 | [NONAME]-[__PyCallClassMemberFunc_ByCString] --> 307 | 140ae92a0 | [NONAME]-[PyCallClassMemberFunc] --> 227 | 1402da2c0 | [NONAME]-[NetworkStream::OnProcess] --> 469 | 140577360 | [NONAME]-[NetworkStream::Process] --> 285 | 140103660 | [NONAME]-[Application::Process] --> 423 | 140104520 | [NONAME]-[Application::Loop] --> 701 | 14013c1e0 | [NONAME]-[appLoop] --> 313 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d4ffc0 | [NONAME]-[PyEval_EvalCodeEx] --> 3608 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 2122 | 140d4ffc0 | [NONAME]-[PyEval_EvalCodeEx] --> 3608 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 3013 | 140d4ffc0 | [NONAME]-[PyEval_EvalCodeEx] --> 3608 | 140d50fc0 | [NONAME]-[PyEval_EvalFrameEx] --> 2122 | 140d4ffc0 | [NONAME]-[PyEval_EvalCodeEx] --> 3608 | 140d46090 | [NONAME]-[PyEval_EvalCode] --> 669 | 140d2a530 | [NONAME]-[PyRun_StringFlags] --> 1348 | 140aeefd0 | [NONAME]-[CPythonLauncher::RunLine] --> 183 | 140aef080 | [NONAME]-[CPythonLauncher::RunMemoryTextFile] --> 160 | 140aef220 | [NONAME]-[CPythonLauncher::RunFile] --> 177 | 1403f5d40 | [NONAME]-[RunMainScript] --> 328 | 1403f6400 | [NONAME]-[Main] --> 364 | 1403f6880 | [NONAME]-[WinMain] --> 417 | 1410f829c | [NONAME]-[__scrt_common_main_seh] --> 288 7fff4a822560 KERNEL32!BaseThreadInitThunk 7fff4c20aa30 ntdll!RtlUserThreadStart


Faulting application name: NONAME.exe, version: 1.0.0.0, time stamp: 0x65e7300f Faulting module name: KERNELBASE.dll, version: 10.0.22621.3235, time stamp: 0x2b72307b Exception code: 0xc0000005 Fault offset: 0x000000000008652b Faulting process id: 0x0x3C4C Faulting application start time: 0x0x1DA6F0BCA2F2B7E Faulting application path: C:\Users\Version001\Desktop\Proje\X64SV\Clientside\Binary\NONAMEX64.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 39fe59ee-6759-4fd3-8276-b71a8ff65c00 Faulting package full name: Faulting package-relative application ID:

Arturo-Intel commented 3 months ago

@Denizeri24 Hello, thanks for contacting us. Can you share a copy of your game? Would help a lot to do some tests on our side.

EDIT: In case you don't want to share your game, could you create a small project just to reproduce the failure? Thanks

-- r2

Denizeri24 commented 3 months ago

@Denizeri24 Hello, thanks for contacting us. Can you share a copy of your game? Would help a lot to do some tests on our side.

EDIT: In case you don't want to share your game, could you create a small project just to reproduce the failure? Thanks

-- r2

Hello, here you can download;

https://www.mediafire.com/file/1u48e96w1uehw8l/Binary.7z/file

extract files and download this and copy files inside to binary folder;

https://www.mediafire.com/file/k861wvf1t3t68vs/Example.7z/file

The exe in the native binary.7z is the one with ASLR turned off. it can open but crashes when it reaches 1.3 GB of memory usage. The 2nd file is the ASLR active one, this one crashes during launch.

Denizeri24 commented 3 months ago

@Arturo-Intel I can give directly project file (source codes) via P.M (of course if not shared public) (intel c++ w/ vs 2022)

Arturo-Intel commented 3 months ago

Sure, add me on discord 277493316105535500

Denizeri24 commented 3 months ago

Sure, add me on discord 277493316105535500

how can add with this ID? idk discord soo much.. I trying to send friend request but its giving error

Arturo-Intel commented 3 months ago

ok... try this

mrr2d2