-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Another crash "can't resolve local ptr to SyntaxNode" #4055
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
Comments
What's the project? Can you reproduce the crash by running |
Also, can you post the full stacktrace? (Ideally run with the nightly version to get a usable stack trace.) |
Yeah I didn't include it because it's just |
Try a nightly build for better stack traces. |
I switched to nightly and it still doesn't give a useful backtrace. |
Well, what about the other questions? Is the crash reproducible using either of the commands, and is there a project we can check out to do so? |
Unfortunately this particular project is closed source. Running Output so far:
This fn install_callback_provisional(
&self,
integration: ProvisionalIntegration,
provider_id: Uuid,
reference: &str,
check_id: Uuid,
expires_in: Duration,
one_time: bool,
) -> Result<(), ()> {
use crate::database::schema::pending_callbacks;
let expiry = self.now() + expires_in;
let num_inserted = self.0.execute("install_callback_provisional", |conn| {
self.pg_delete_expired_callbacks(conn)?;
// Install our new callback
diesel::insert_into(pending_callbacks::table)
.values((
pending_callbacks::provider_id.eq(provider_id),
pending_callbacks::reference.eq(reference),
pending_callbacks::one_time.eq(one_time),
pending_callbacks::check_id.eq(check_id),
pending_callbacks::expiry.eq(expiry),
pending_callbacks::provisional_name.eq(integration.provider_name),
pending_callbacks::provisional_version.eq(integration.protocol_version as i32),
pending_callbacks::provisional_secret_key.eq(integration.secret_key),
))
.on_conflict_do_nothing()
.execute(conn)
});
if num_inserted == 1 {
Ok(())
} else {
Err(())
}
} |
The performance should hopefully be improved by the next nightly, maybe you can try it again then. |
It finally finished:
|
I saw this error randomly when I was browsing in RA too. (master ec645f2) backtrace
|
Ran into this with last current master (363c1f2) and It crashes pretty reliably. Project code is here: https://github.com/openethereum/openethereum Backtrace:
Running
The
Running
|
Is If so, it might be #4315 |
It is indeed. And toggling seems to help so far! |
Seems to work great now with |
Haven't seen this one reported yet:
The text was updated successfully, but these errors were encountered: