You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Stack overflow on Windows during "many providers" test #925
Describe the bug
After migrating to material_ui in #924, the test "MultiProvider Supports a large number of providers" is failing on Windows. This was discovered when run as part of the Flutter SDK's customer tests in flutter/tests#498.
| ::group::❌ C:/Users/RUNNER~1/AppData/Local/Temp/flutter_customer_testing.provider.feaa7449/tests/packages/provider/test/null_safe/multi_provider_test.dart: MultiProvider Supports a large number of providers (failed)
| ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
| The following FormatException was thrown building _InheritedProviderScope<int?>:
| Stack overflow
| ^#(\d+) +(.+) \((.+?):?(\d+){0,1}:?(\d+){0,1}\)$
|
| The relevant error-causing widget was:
| _InheritedProviderScope<int?>
| _InheritedProviderScope:file:///C:/Users/RUNNER~1/AppData/Local/Temp/flutter_customer_testing.provider.feaa7449/tests/packages/provider/lib/src/inherited_provider.dart:164:12
|
To Reproduce
Run the test on windows:
flutter test test/null_safe/multi_provider_test.dart --plain-name "Supports a large number of providers"
Expected behavior
I expect the test to pass consistently. The upgrade to material_ui should have changed very little or nothing about this test to cause a stack overflow.
The test is just using a very large stack on purpose. It was likely very close to hitting the CI's limit before, and with material_ui, the widget tree maybe got a tiny bit bigger, causing the test to go over the stack limit.
This is very low priority for me, so don't expect a fix. I'd suggest just disabling said test.
Activity
rrousselGit commentedon Oct 1, 2026
The test is just using a very large stack on purpose. It was likely very close to hitting the CI's limit before, and with material_ui, the widget tree maybe got a tiny bit bigger, causing the test to go over the stack limit.
This is very low priority for me, so don't expect a fix. I'd suggest just disabling said test.
justinmc commentedon Oct 1, 2026
I'll open a PR here to skip it, thanks.
justinmc commentedon Oct 2, 2026
Actually, I will just skip in in flutter's CI in flutter/tests#498.