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

Uncaught RangeError: Maximum call stack size exceeded at Array.toString (native) #528

Closed
ratiw opened this issue Jan 17, 2018 · 4 comments
Closed

Uncaught RangeError: Maximum call stack size exceeded at Array.toString (native) #528

ratiw opened this issue Jan 17, 2018 · 4 comments
Labels
bug

Comments

@ratiw
Copy link

ratiw commented Jan 17, 2018

Version

4.0.0

Browser and OS info

Chrome 63.0.3239.132 (Official Build) (64-bit) / Windows 10

Steps to reproduce

  • Go to this url to view the sample project on CodeSandbox.io
  • Right-click the page and select "Inspect"
  • In the Developer Tools window, click Vue menu to display Vue-Devtools
  • Click on <app> on the left pane, the right pane should not cause any error
  • Click on <Vuetable> node or its child component <VuetableRowHeader>, and it dumps error out in the console pane

What is expected?

Vue-Devtools should display info about the selected component.

Before 4.0.0, this never happens.

What is actually happening?

The following error shows up in console pane

backend.js:1 Uncaught RangeError: Maximum call stack size exceeded
    at Array.toString (native)
    at D (chrome-extension://nhdogjmejiglipccpnnnanhbledajbpd/build/backend.js:1:20128)
...

The old version of Vue-Devtools (before 4.0) was working fine without any error showing up.
@ibyteyou
Copy link

ibyteyou commented Jan 17, 2018 •
edited
Loading

+1
maybe it somehow depends on the circular references into component data.
components in components...

screenshot

@filipesarturi
Copy link

Same problem here

@Akryum Akryum added the bug label Jan 18, 2018
@haoxutong
Copy link

same problem here

Akryum pushed a commit to Akryum/vue-devtools that referenced this issue Jan 19, 2018
Fix vuejs#528
984ce87
@Akryum Akryum closed this as completed Jan 19, 2018
@Akryum Akryum mentioned this issue Jan 19, 2018
Merged
@Akryum
Copy link
Member

Akryum commented Jan 19, 2018

You can test this branch: https://github.com/Akryum/vue-devtools/tree/types-improvements

@ratiw ratiw mentioned this issue Jan 20, 2018
Closed
Akryum pushed a commit that referenced this issue Jan 22, 2018
Serialization & Types improvements (#523)
842aa35 
* More fault tolerant

* Display stores with CustomValue API

* Dsiplay VueRouter instances with CustomValue API

* CustomValue API: new 'tooltip' option, supports functions, component def

* Test router & store

* Open in editor Component defs

* Fix #528

* Comments

* Encode cache clear

* Large array test

* CustomValue API: respect fields order

* Switch props and data sections to follow style guide

* New 'grey' and 'red' classes

DataField: allowing to reproduce current available styling using CustomValue API

* Add support for Map and Set - Fix #349

Initial PR #490 by AdamNiederer

* Set and Map test case

* Fix Map key/value inverted

* Optimizations

* Fix tooltip

* DataField style changes

* Env: added isLinux & isWindows + function 'f' style fixes

* gps-not-fixed icon is ugly on Windows

* Style tweaks

* Typo

* Added more function test cases
This was referenced Jan 24, 2018
Closed
Closed
@zhanziyang zhanziyang mentioned this issue Jan 27, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@ratiw @Akryum @filipesarturi @haoxutong @ibyteyou