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

Session crashes with unhandled error after running overnight on macOS 12.0.1 #1982

Open
georgemaschke opened this issue Oct 25, 2021 · 4 comments

Comments

@georgemaschke
Copy link

After running overnight, Session crashes with an unhandled error notice: "Error: ENOENT: no such file or directory, open '/Users/myAccount/Library/Application Support/Session/logs/log.log'"

Despite the notice, no such logs directory or file exists.

I have returned to Session on two consecutive mornings to be greeted with this error.

image

  • Device: Macintosh with Intel processor
  • OS: macOS 12.0.1
  • Session Version or Git commit hash: v1.7.3
@Bilb
Copy link
Collaborator

Bilb commented Oct 27, 2021

This is related to the logger library in use in Session. trentm/node-bunyan#374.
I don't reproduce this issue on my side but implemented the fixes people are talking in that issue.
Would you mind giving a non official build a try to see if that fixes your issue?
If you're fine, can you reach out to me on Session (id is in my github status), or just search me on session, i.e. just the letter b :)

Bilb added a commit to Bilb/session-desktop that referenced this issue Oct 27, 2021
Bilb added a commit to Bilb/session-desktop that referenced this issue Oct 27, 2021
@georgemaschke
Copy link
Author

Bilb, thank you for your attention to this. At the moment, being new to Session, I'd prefer to stick to official builds. I'm now on v1.7.4 and have not yet encountered this issue.

@Bilb
Copy link
Collaborator

Bilb commented Nov 4, 2021

ok, closing this. let me know if it happens again

@Bilb Bilb closed this as completed Nov 4, 2021
@yougotwill
Copy link
Collaborator

@Bilb This issue has returned. Attempted to debug it and it seems to happens when the log directory in the userData folder gets deleted for whatever reason. The rotation just tries to run despite the file not existing. We need a way to either cancel the rotation stream if we notice the folder doesn't exist or use an alternative log rotation package.

@yougotwill yougotwill reopened this May 27, 2022
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

3 participants