-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
DisposalException from the plugin in 2021.1 EAP #248
Comments
@east825
Would you please show me an example?
I can catch |
Sure, I meant adding something like:
inside In general, it's a good idea to do it whenever you need to access an SDK in a postponed/background activity (it might become invalid by this moment). We actually started getting more of such exceptions in various other places, I'm investigating what's going on. There is likely a deeper problem on our side (apparently, we dispatch events for an already disposed SDK), but this is an easy fix to protect your plugin against it. |
I have fixed it. Did you get the error report by users? |
It's from exception reports users submit directly from an IDE. As far as I
see, it hasn't been reported on YouTrack yet.
…On Fri, Feb 26, 2021 at 2:36 PM Koudai Aono ***@***.***> wrote:
I have fixed it.
Thank you!!
Did you get the error report by users?
Would you please share the issue if the ticket of issue exits on youtrack?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#248 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHV7RHHASUCHXFIKG4RHUDTA6BUNANCNFSM4YEEPXYQ>
.
--
Best regards
Mikhail Golubev
|
I see. Thank you |
The Fixed version has been published in the market. |
We get a lot of exception reports like the following in 2021.1 EAP. The easiest way to fix this is to check that an SDK is not disposed in the runnable launched with
invokeLater
.The text was updated successfully, but these errors were encountered: