-
Notifications
You must be signed in to change notification settings - Fork 15.5k
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
Notification close() causes app crash at exit #18701
Comments
This is not in itself a reproducible piece of code, as it doesn't give me enough context about how you're using it. Please attach a more complete piece of error-inducing code for the maintainers to triage this issue. I put:
in a quick-start main process and could not reproduce this. |
@codebytere could you try this: let count = 0
send(title, body) {
const notif = new Notification({title: title, body: body, silent: true})
notif.once('click', () => console.log('tick'))
notif.show()
setTimeout(() => {notif.close(); if (count === 5){app.quit()}}, 10000)
}
setInterval(() => {this.send('test', 'test'); count += 1},15000) |
Fwiw I think I reproed this (either that or I found a different notification crash). I think it might be related to my recent notification reset fix |
Repro'd successfully @johaven, thanks! Crash report:
|
We are seeing something similar. We symbolicated the trace and got the following:
|
@abettadapur based on your crash log, i think you might be experiencing this extremely similar (and possibly duplicate) issue: #19842 |
Expected Behavior
Electron does not crash at exit.
Actual Behavior
The notifications are sent well, i use the close() function to avoid persistence in Notification Center.
By doing this every time I quit the application I have a message that warns me that the application did not stop properly.
To Reproduce
After sending notification(s), close application (app.quit()) and the error will appear.
To no longer have the error after quitting app, i do not use the function close () but my application generates a lot of notifications and I would have preferred to handle that.
The text was updated successfully, but these errors were encountered: