-
Notifications
You must be signed in to change notification settings - Fork 2
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
segmentation fault (core dumped) #5
Comments
Thanks for the bug reports, I will be making my way through them. I have a couple questions about this one.
|
im not sure about luajit, (I'll get more info soon) and I dont yet know why
this crash occurs; its happened a few times, but never while Ive been
playing so I dont know the context yet.
…On Tue, Feb 22, 2022 at 10:25 PM Quentin Quaadgras ***@***.***> wrote:
Thanks for the bug reports, I will be making my way through them. I have a
couple questions about this one.
1. Does this crash happen randomly?
2. Do you have LuaJIT?
—
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOSK5KGRTRM36QWHPMIDIVTU4RHRZANCNFSM5PBKT3YA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
If this continues, i will post more info, but overall, best not to worry
about this one until we have more info about it.
…On Thu, Feb 24, 2022 at 3:18 PM Gaudeor Rudmin ***@***.***> wrote:
im not sure about luajit, (I'll get more info soon) and I dont yet know
why this crash occurs; its happened a few times, but never while Ive been
playing so I dont know the context yet.
On Tue, Feb 22, 2022 at 10:25 PM Quentin Quaadgras <
***@***.***> wrote:
> Thanks for the bug reports, I will be making my way through them. I have
> a couple questions about this one.
>
> 1. Does this crash happen randomly?
> 2. Do you have LuaJIT?
>
> —
> Reply to this email directly, view it on GitHub
> <#5 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AOSK5KGRTRM36QWHPMIDIVTU4RHRZANCNFSM5PBKT3YA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
segmentation fault (core dumped)
thats the only error I get for this crash.
I have been told that this is caused by an improper use of the api somewhere, but IK thats not particularly helpful. Maybe we can find out what causes it.
I wouldnt worry about it until there is more info
The text was updated successfully, but these errors were encountered: