Comment #13 on issue 3491 by [email protected]: Debugger cannot evaluate
stack-allocated local variables from outer scopes.
https://code.google.com/p/v8/issues/detail?id=3491
I can think of use cases (for example, when the developer can reproduce the
issue being debugged after a page refresh) in which having a button/option
to "deoptimize the code and restart" would be good enough. The user
experience would be similar to the way the tab with the Network debugger
requires you to refresh the page - a little bit inconvenient, but better
than nothing or forcing a developer to perform an update of the code on a
production server:) Similarly if I want the profiler to profile my code I'm
OK with hitting F5, and even expect it to work it that way, and a little
bit of slow-down.
The optimization could be turned on again once I close the devtools (which
would also be a familiar behaviour, as for example "Toggle device mode"
works this way) in order to prevent one from accidentally leaving the
browser in a permanently "deoptimizing" state.
I'm writing all this in order to convince you that there is a way to
implement this feature which is not "confusing/surprising" to the developer
- I think this is more a UX/expectations managment/wording issue.
As to the proposition from #12 - is it even possible to perform this? Is it
possible that unrefrenced objects from outer scopes are already garbage
collected at this point?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
