Repository navigation
Crash while reading an obfuscated stack trace > flutter symbolize > Cannot locate isolate instructions section in snapshot #191879
Description
Description
this issue follows after #191205
flutter symbolize cannot find isolate instruction.
Exception throws in native_stack_traces-0.6.1 > lib > src > dwarf.dart
...
case InstructionsSection.isolate:
final isolateStart = isolateStartAddress(pcOffset.architecture);
if (isolateStart == null) {
throw 'Cannot locate isolate instructions section in snapshot';
}
...
Steps to reproduce
- create new flutter project from template
- throw an exception
void _incrementCounter() {
try {
throw UnimplementedError("foobar");
} catch (e, st) {
print(st);
}
- build apk
flutter build apk --release --obfuscate --split-debug-info=debuginfo/ - run app (android), push button and save stacktrace to file
- try to read the obfuscated stack trace
command
flutter symbolize --debug-info .\debuginfo\app.android-arm64.symbols -i .\stacktrace.txt
output
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 3941, tid: 538349158472, name 1.ui
os: android arch: arm64 comp: yes sim: no
build_id: '387877b8cc0fc6ef24a2e307d53e83c0'
isolate_dso_base: 79eaa46000, vm_dso_base: 0
isolate_instructions: 79eaaf6000, vm_instructions: 0
Failed to symbolize stack trace:
Cannot locate isolate instructions section in snapshot
flutter doctor
3.47.1 with manual applied patch in symbolize.dart
[√] Flutter (Channel stable, 3.47.1, on Microsoft Windows [Version 10.0.26200.9168], locale de-DE) [343ms]
• Flutter version 3.47.1 on channel stable at H:\SDK\Flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 6655482ec0 (8 days ago), 2026-08-19 10:07:23 -0700
• Engine revision 5d53178869
• Dart version 3.13.1
• DevTools version 2.60.0
• Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android, enable-ios, cli-animations, enable-native-assets, enable-record-use, enable-swift-package-manager,
omit-legacy-version-file, enable-lldb-debugging, enable-uiscene-migration
[√] Windows Version (11 Pro 64-bit, 25H2, 2009) [2,1s]
[√] Android toolchain - develop for Android devices (Android SDK version 36.0.0) [3,0s]
• Android SDK at H:\SDK\Android\Sdk
• Emulator version 37.1.11.0 (build_id 15917651) (CL:N/A)
• Platform android-37.0, build-tools 36.0.0
• ANDROID_HOME = H:\SDK\Android\Sdk
• Java binary at: H:/SDK/jdk-17.0.12\bin\java
This JDK is specified in your Flutter configuration.
To change the current JDK, run: `flutter config --jdk-dir="path/to/jdk"`.
• Java version Java(TM) SE Runtime Environment (build 17.0.12+8-LTS-286)
• All Android licenses accepted.
[√] Chrome - develop for the web [97ms]
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.12.3) [96ms]
• Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
• Visual Studio Community 2022 version 17.12.35527.113
• Windows 10 SDK version 10.0.22621.0
[√] Connected device (3 available) [1.641ms]
• Windows (desktop) • windows • windows-x64 • Microsoft Windows [Version 10.0.26200.9168]
• Chrome (web) • chrome • web-javascript • Google Chrome 151.0.7922.172
• Edge (web) • edge • web-javascript • Microsoft Edge 151.0.4129.107
[√] Network resources [1.744ms]
• All expected network resources are available.
• No issues found!
Activity
moodstubos commentedon Aug 27, 2026
Bugfix release 3.47.2 just came out that includes fix for #191205.
same issue as with 3.47.1.
mbcorona commentedon Aug 27, 2026
Hi @moodstubos, thanks for the report. Routing to the tool team.
Reproduced on macOS with a clean, ABI-matched build (stable 3.47.0): flutter symbolize fails on the obfuscated trace, but #191205 ("Bad state: Future already completed") fires first and swallows the underlying erro, so the "Cannot locate isolate instructions section" message only surfaces once #191205 is patched. The throw itself originates upstream in native_stack_traces (dwarf.dart), where isolateStartAddress() returns null.
Effectively blocked by #191205; worth triaging the two together.
mraleph commentedon Aug 28, 2026
There were changes to
native_stack_tracesdue to removal of vm-isolate but these changes were not released on pub and consequently not rolled into Flutter. I suspect that't the reason for this crash.cc @rmacnak-google @sstrickl
moodstubos commentedon Sep 3, 2026
@mbcorona
The symbol files cannot be read by older Flutter versions, too. I think the problem is how the debug info symbol files are generated.
Maybe this should be routed to the team-android team instead?
This issue makes it impossible to read obfuscated stack traces when app was created with current stable version >3.47
mraleph commentedon Sep 3, 2026
@moodstubos the reason is explained above. there was a change in the structure of snapshot, which requires upgrading one of the packages the flutter tool depends on
sstrickl commentedon Sep 4, 2026
Making a CL to bump the version, since that didn't happen when the VM isolate removal changes were landed. Once that lands, I'll re-publish.
[pkg/native_stack_traces] Bump version for VM isolate removal changes.
sstrickl commentedon Sep 7, 2026
It's been published now, going to give it a bit for propagation and then I'll ready a pull request for updating the package dependencies in Flutter.