-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
The app is crashing no matter what #159
Comments
Same on Mac |
Fedora 35 works normally, at least freshly installed |
Same here: app instantly closes without any window appearing. And there's no way to get it running. |
Guys can you reckec on MacOS? |
Hey @DEgITx! CleanShot.2022-08-28.at.13.55.20.mp4 |
Hey @DEgITx! |
Can you please clarify arch of the mac os version. If it arm64, there is still no support, but planned. |
Hi @DEgITx! |
I've just tried to run this program again on a Intel-based mac and macOS 13 and it still crashes. Here's crashlogs There are this lines:
After that I've tried on an arm-based mac and it also crashes with the same message. |
I tryed to open it in Windows, but it closes immideatly, without even showing the interface. I can only see in the task manager, that the Rats process is appears and disappears in a moment. |
@TuTAH1 please create new issue and attach rats.log from appdata folder |
Hey @DEgITx |
|
New comment here - new try to run this app on a newer macOS :D For whatever reason this app tries to run x86-64 version of the included binaries by default even despite there are arm versions lying nearby already. And any such a run results in the instant app crash with the message in the log which is shown above and the couple of messages in an internal macOS' app "Console" with that error:
I've tried to mask those x64 binaries for app to not to use them by simply renaming the corresponding folder but the app throws an 'ENOENT' error to me which means it can't find a file\folder and thus can't spawn a "searchd" process. And then it just hangs up. No interface and no any other actions from the app occurs. The only way to close it then is the force kill via the "System Monitor" app.
So it only tries to load files from x64 folder.
Sooo... looks like this app desperately wants those To conclude:
@DEgITx please take a look, hope it helps :) |
Regardless my 2-nd conclusion above. rats-search/src/background/electronAppPath.js Lines 54 to 58 in cbda746
Since the whole app is an Intel-one and runs under Rosetta I assume the value that Node returns in that check is not arm64 but x86-64. So this check fails and the next check which checks only the platform and not the architecture returns an x64 sub-directory. I've found this issue in a Node's GH that probably has a solution for that situation: nodejs/node#41900 (comment) |
no matter how much time i click the exe file/reinstall it or disable the antivirus it just doesn't work.
i tried running the same installer in a sandbox and it somehow worked, i dont understand what is the problem
The text was updated successfully, but these errors were encountered: