-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Dart FFI crashes on ScopeBuilder::LookupVariable #56412
Comments
Summary: The |
edit the stack trace to include the full trace. |
@bsutton Thanks for the repro! I can reproduce this locally. (off-topic: Don't use Ingredients for small repro: |
(off-topic: the person who have written those |
(off-topic: 🤣 I had an eerie was feeling |
Any news on this issue @dcharkes? |
I have a minimal example repro. And I believe the bug is in the scope builder (the minimal repro sails through the scope builder and crashes later), but I need to reverse engineer what the scopes should be. |
Do we know what version of dart this will be published in? Is it likely to be back ported to prior dart versions? |
Version 3.6.0-173.0.dev (or later)
The chance of hitting these bugs is quite small, using a named argument in earlier position, nested functions, and finalizable in a single repro. I doubt anyone else is hit by this. Are you in need of a cherry pick for stable or can you use Dart dev / Flutter master @bsutton? |
I use the package in dcli which has a reasonable sized user base.
Popularity on pub.dev of 94%
…On Mon, 26 Aug 2024, 5:58 pm Daco Harkes, ***@***.***> wrote:
Do we know what version of dart this will be published in?
Version 3.6.0-173.0.dev (or later)
Is it likely to be back ported to prior dart versions?
The chance of hitting these bugs is quite small, using a named argument in
earlier position, nested functions, and finalizable in a single repro. I
doubt anyone else is hit by this.
Are you in need of a cherry pick for stable or can you use Dart dev /
Flutter master @bsutton <https://github.com/bsutton>?
—
Reply to this email directly, view it on GitHub
<#56412 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG32OETXCNXBXWOA3Y2GMLZTLNZHAVCNFSM6AAAAABMHSJSE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBZGU4DKMBVGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@mraleph Any opinions? I can create a cherry pick if we want to get this in to 3.5. |
I'm working on the native_sychronise package to add in timeouts.
The package makes ffi calls into the posix system.
Merging the latest changes from upstream are causing a segfault and the stack trace seems to indicate a dart/ffi issue.
I've tested the code against dart 3.5.0 and 3.4.0 with the same crash occurring.
I've created a branch of the project that will reproduce the issue:
https://github.com/onepub-dev/native_synchronization/tree/ffi-crash
To reproduce the problem run the ' mailbox - timeout' unit test in 'mailbox_test.dart.
The presence of line 148 in mailbox.dart causes the crash.
Simply commenting out this line and the code no longer crashes.
The text was updated successfully, but these errors were encountered: