Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Luxmark does not check for errors returned by driver when it fails to allocate memory. This causes the app to crash. Typically seen with limited GPU memory ( ~1 GB) in VM setup. #4

Open
dibasc opened this issue May 17, 2019 · 0 comments

Comments

@dibasc
Copy link

dibasc commented May 17, 2019

When FB is restricted to make available free video memory as ~160Mib, luxmark app is crashing on win7, win8.1 and win10.
In all the cases nvidia driver is returning proper error (not able to allocate memory). Following is the debugging info
from eventviewer and windbg logs when the application crashes.

Config Used:
Quadro GV100 + cuda_a-190502-26255178.

On Win7 and win8.1,
Event viewer and windbg shows faulting module as luxmark.exe.
BUGCHECK_STR INVALID_POINTER_READ.
ExceptionCode: c0000005 (Access violation).
Full crashdump is available at \devrel\share\ngubba\luxmark_crash\luxmark.exe.5272.

On Win10 RS4
Event viewer and windbg shows faulting module as MSVCR120.dll.
BUGCHECK_STR: FAIL_FAST_FATAL_APP_EXIT.
ExceptionCode: c0000409 (Security check failure or stack buffer overrun).
Full crashdump is available at \devrel\share\ngubba\luxmark_crash\luxmark.exe.12656.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@Dade916 Dade916 transferred this issue from LuxCoreRender/LuxCore Aug 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant