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

[Bug]: Internal Crash #3113

Open
1 of 3 tasks
RXHI10 opened this issue Jan 2, 2025 · 44 comments
Open
1 of 3 tasks

[Bug]: Internal Crash #3113

RXHI10 opened this issue Jan 2, 2025 · 44 comments
Assignees
Labels
Crash Issues that are causing unexpected termination, and crashes OS: Windows 11 Waiting for requester If waiting for a long time it is reasonable to close an issue

Comments

@RXHI10
Copy link

RXHI10 commented Jan 2, 2025

JASP Version

0.19.2

Commit ID

No response

JASP Module

Unrelated

What analysis are you seeing the problem on?

No response

What OS are you seeing the problem on?

Windows 11

Bug Description

Internal crash issue

Expected Behaviour

Solve the internal crash

Steps to Reproduce

1.Reopening the Application
2.
3.
...

Log (if any)

No response

More Debug Information

No response

Final Checklist

  • I have included a screenshot showcasing the issue, if possible.
  • I have included a JASP file (zipped) or data file that causes the crash/bug, if applicable.
  • I have accurately described the bug, and steps to reproduce it.
Copy link

github-actions bot commented Jan 2, 2025

@RXHI10, thanks for taking the time to create this issue. If possible (and applicable), please upload to the issue website (#3113, attaching to an email does not work) a screenshot showcasing the problem, and/or a compressed (zipped) .jasp file or the data file that causes the issue. If you would prefer not to make your data publicly available, you can send your file(s) directly to us, issues@jasp-stats.org

@github-actions github-actions bot added the Waiting for requester If waiting for a long time it is reasonable to close an issue label Jan 2, 2025
@boutinb
Copy link
Contributor

boutinb commented Jan 2, 2025

Hi @RXHI10 , without more information, we cannot help you...

@tomtomme tomtomme removed the Bug label Jan 2, 2025
@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@github-actions github-actions bot removed the Waiting for requester If waiting for a long time it is reasonable to close an issue label Jan 24, 2025
@boutinb
Copy link
Contributor

boutinb commented Jan 24, 2025

We cannot see your picture. If you want to add a picture, you have to drag & drop it in GitHub.

@boutinb boutinb added the Waiting for requester If waiting for a long time it is reasonable to close an issue label Jan 24, 2025
@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025

Image

See this image and please fix

@github-actions github-actions bot removed the Waiting for requester If waiting for a long time it is reasonable to close an issue label Jan 24, 2025
@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@EJWagenmakers
Copy link
Collaborator

I'll anticipate the response from the team: in order to fix this problem, we need a reproducible path to the error. To get this path, it helps if we have all the information you can provide. Specifically, we need to know when the error occurs and for what analysis; also, it would greatly help if you could provide the data that produced this error. We can only fix errors we can reproduce...
Cheers,
EJ

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@EJWagenmakers
Copy link
Collaborator

So you also get this error with other data files? Also with a data file from the JASP Data Library?
Before we can fix the problem we need to identify it; you are one of the first users to report this problem, and therefore I suspect it may be specific to the data or your setup somehow. This is what we need to figure out.
EJ

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@EJWagenmakers
Copy link
Collaborator

Any csv file? Could you attach the csv file?
The easiest/fastest way to solve this is to see whether there is something strange about the file. I am willing to look at this but you need to help me out as much as you can. It does not help to call because in that call I would just ask you to send along the csv file :-)

EJ

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025

SalesSalary (1).csv

Image

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025

Image

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025

where are you. plz help me. I am worried

@EJWagenmakers
Copy link
Collaborator

So I do not have any crashes, but I will note that the ANOVA you conduct will complain, because "position" is not a scale variable (as ANOVA demands). Also, the fixed factors are not factors but scale variables. So I get this error message:

Image

When I do descriptives this works fine for me. I am not sure about the Z-test you ran: what are the input values? (dependent variable?).

Also, I noticed that your file is called SalesSalary.1.csv. I can't imagine this is the problem but I would rename it so that it has only a single period (SalesSalary1.csv, for instance). I am running this in Windows under 0.19.3 though.
EJ

@EJWagenmakers
Copy link
Collaborator

And actually, to renew my question: do you get crashes when you open a file from the JASP Data Library? This is really important to know, because if you do get crashes there, we can rule out a peculiarity of the data as the source of the problem.

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025

Image
again i am having this error..... about the library thing I actually donot require any file from there. all i need to do is perform from my imported file

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025

and can you do the anova testing for the file. As it will clear my doubt of where i am doing wrong and maybe beneficial for telling you the problem more better

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025

Image

This is it when I have performed the ANOVA test perfectly. hence proved it is an actaul error from the GitHub side....Plz resolve

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@EJWagenmakers
Copy link
Collaborator

EJWagenmakers commented Jan 24, 2025

Strange. I think our programmers would need more information, but I am sure they will ask for it. [edited out the part where I ask about the Mac, because you said you were running Windows]

@EJWagenmakers
Copy link
Collaborator

So actually, can you send me the latest csv that the correct ANOVA is based on? And tell me what variables you dragged to what boxes? Also, I realize you do not NEED the files from the Data Library. But if you test them and you do NOT get a crash this means the problem is located with the data fie. If you DO get a crash the problem is generic. So this is a highly diagnostic test.

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025

[

SalesSalary (1).csv

This was the file.....And again when the window got exited I did again and since this time it was fast, therefore it saved early and not internal crash error thing came

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025

Image
again the same error came

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025

Image

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@RXHI10
Copy link
Author

RXHI10 commented Jan 24, 2025 via email

@shun2wang
Copy link
Contributor

I noticed you load from oneDriver folders, you can try load it from another folders and see if it still happened.

@shun2wang
Copy link
Contributor

But I also have to let you know that you have to pay attention to the advice above provided by EJ and check if there are other files with this problem or just this file.

@RXHI10
Copy link
Author

RXHI10 commented Jan 25, 2025 via email

@shun2wang
Copy link
Contributor

@RXHI10
Copy link
Author

RXHI10 commented Jan 25, 2025 via email

@RXHI10
Copy link
Author

RXHI10 commented Jan 25, 2025 via email

@RXHI10
Copy link
Author

RXHI10 commented Jan 25, 2025 via email

@tomtomme
Copy link
Member

@RXHI10
what do you mean by "over there"? If you still experience the problem pls report back, ideally with the log files. But please also tell us if the error went away. We are currently swamped by these crash reports and have no clue why

@tomtomme tomtomme added Waiting for requester If waiting for a long time it is reasonable to close an issue Crash Issues that are causing unexpected termination, and crashes labels Feb 27, 2025
@RXHI10
Copy link
Author

RXHI10 commented Feb 28, 2025 via email

@github-actions github-actions bot removed the Waiting for requester If waiting for a long time it is reasonable to close an issue label Feb 28, 2025
@tomtomme
Copy link
Member

we like what we do, and do it open source and for free - I think out there is no one throwing money at us atm to do so as you suggest :D

@tomtomme tomtomme added the Waiting for requester If waiting for a long time it is reasonable to close an issue label Feb 28, 2025
@RXHI10
Copy link
Author

RXHI10 commented Feb 28, 2025 via email

@github-actions github-actions bot removed the Waiting for requester If waiting for a long time it is reasonable to close an issue label Feb 28, 2025
@tomtomme
Copy link
Member

tomtomme commented Feb 28, 2025

@RXHI10
I do not mind, do not worry! I understand your point of view and of course open source is always a challenge - but a fun one! And it is exactly fun BECAUSE it is mostly not about the money!

@tomtomme tomtomme added the Waiting for requester If waiting for a long time it is reasonable to close an issue label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Crash Issues that are causing unexpected termination, and crashes OS: Windows 11 Waiting for requester If waiting for a long time it is reasonable to close an issue
Projects
None yet
Development

No branches or pull requests

5 participants