Skip to content
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.

Sign up for GitHub

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

Jump to bottom

subtreeContext exception after pressing back button twice #5632

Closed
jason-simmons opened this issue Aug 26, 2016 · 7 comments
Closed

subtreeContext exception after pressing back button twice #5632

jason-simmons opened this issue Aug 26, 2016 · 7 comments
Assignees
@Hixie

Comments

@jason-simmons
Copy link
Member

Run Gallery in debug mode. Enter Shrine, and click on one of the product tiles. Press the Back button twice in quick succession.

This produces the exception below.

The same thing happens if I click on a recipe in Pesto and hit Back twice.

The bug is timing sensitive - I haven't seen it happen in profile mode

I/flutter : ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter : The following NoSuchMethodError was thrown during a scheduler callback:
I/flutter : The null object does not have a getter 'subtreeContext'.
I/flutter : NoSuchMethodError: method not found: 'subtreeContext'
I/flutter : Receiver: null
I/flutter : Arguments: []
I/flutter : When the exception was thrown, this was the stack:
I/flutter : #0 Object._noSuchMethod (dart:core-patch/object_patch.dart:44)
I/flutter : #1 Object.noSuchMethod (dart:core-patch/object_patch.dart:47)
I/flutter : #2 HeroController._updateQuest (package:flutter/src/widgets/heroes.dart:527)
I/flutter : #3 BindingBase&SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:535)
I/flutter : #4 BindingBase&SchedulerBinding.handleBeginFrame (package:flutter/src/scheduler/binding.dart:503)
I/flutter : #5 _beginFrame (file:///ssd2/sky/engine/src/flutter/lib/ui/hooks.dart:48)
I/flutter : ════════════════════════════════════════════════════════════════════════════════════════════════════
@jason-simmons
Copy link
Member Author

@Hixie

@Hixie Hixie self-assigned this Aug 26, 2016
@Hixie
Copy link
Contributor

Hixie commented Aug 26, 2016

I think I have a fix for that.

@Hixie
Copy link
Contributor

Hixie commented Aug 26, 2016

Specifically #5633

@Hixie
Copy link
Contributor

Hixie commented Aug 26, 2016

Boo, that doesn't actually fix it.

@Hixie
Copy link
Contributor

Hixie commented Aug 27, 2016

Ok the problem here is subtly different. The problem here is that between scheduling the quest update and actually starting the heroes, we are handling a quest completion, which clears our variables and thus we lose track of what we're about to do.

@Hixie
Copy link
Contributor

Hixie commented Aug 27, 2016

ok, actual fix is in that PR now

@Hixie Hixie modified the milestone: Flutter 1.0 Sep 12, 2016
@Hixie Hixie closed this as completed Sep 12, 2016
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Hixie Hixie

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Hixie @jason-simmons