-
Notifications
You must be signed in to change notification settings - Fork 4
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
Crashes in release mode #1
Comments
thanks for reporting. How can I reproduce this error? I'm planning to investigate it asap |
No problem.
I tried compiling OpenSimplex2S into 2 different x86 Win32 Visual Studio
projects - it worked fine in debug but when in release mode crashed at the
noted line.
I remember it was dereferencing the memory at *(latticePoints[ ((int
*)lookup4DPregen[i].data)[j] ]) that caused the access violation. Unless
something very strange is wrong with my PC then just creating a Win32
Visual Studio project, setting it to x86 and release mode and initializing
both a OpenSimplexEnv and OpenSimplexGradients object should be enough to
recreate the bug.
Can I also just note that neither of these objects (OpenSimplexEnv &
OpenSimplexGradients) are POD and there are no functions in your API for
freeing their allocated resources when finished with them.
…On Fri, Apr 7, 2023 at 12:51 AM Marco Ciaramella ***@***.***> wrote:
thanks for reporting. How can I reproduce this error? I'm planning to
investigate it asap
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4RFCMFJOA7OU2I7JAETY3LW75JHFANCNFSM6AAAAAAWOADMN4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Repository owner
deleted a comment
Jan 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When in release mode OpenSimplex2S.cpp crashes at line 1257 with a memory access violation.
((LatticePoint4D *)v.data)[j] = *(latticePoints[((int *)lookup4DPregen[i].data)[j]]);
I don't have the time to hunt down what's going on, which is a shame because this is otherwise nicely written procedural code.
The text was updated successfully, but these errors were encountered: