Skip to content

Message length exceeded maximum allowed length #515

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.

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

Closed
w1ndy opened this issue Jan 15, 2018 · 18 comments
Closed

Message length exceeded maximum allowed length #515

w1ndy opened this issue Jan 15, 2018 · 18 comments
Labels

Comments

@w1ndy
Copy link

w1ndy commented Jan 15, 2018

Version

4.0.0

Browser and OS info

Chrome 63

Steps to reproduce

Put a large amount of data in components and open Vue devtools.

What is expected?

Devtools open correctly.

What is actually happening?

vue-devtools
Error thrown: Message length exceeded maximum allowed length.
Could be similar to this.

@w1ndy
Copy link
Author

w1ndy commented Jan 15, 2018

A minimal repro:

<!DOCTYPE html>
<body>
    <div id="app"></div>
</body>
<script src="https://cdnjs.cloudflare.com/ajax/libs/vue/2.5.13/vue.js"></script>
<script>
new Vue({
    el: '#app',
    mounted () {
        for (let i = 0; i < 10000000; i++)
            this.largeArray.push(i)
    },
    data: {
        largeArray: []
    }
})
</script>

@w1ndy
Copy link
Author

w1ndy commented Jan 15, 2018

vue-devtools completely freezes on this code, and the error will be thrown a moment later.

@Akryum Akryum added the bug label Jan 15, 2018
@Akryum
Copy link
Member

Akryum commented Jan 19, 2018

@w1ndy
Copy link
Author

w1ndy commented Feb 7, 2018

@Akryum Sorry for the late reply, but the patch merged did not resolve this issue... The latest vue-devtools is still throwing errors and violations on the example I gave earlier.

@w1ndy
Copy link
Author

w1ndy commented Feb 7, 2018

Is it possible to not serialize and transfer data entirely, but retrieve their values on demand?

@colinfike
Copy link

I can confirm that I am also still seeing this issue.

@maverickchangithub
Copy link

@colinfike I got the same issue in a PC environment , but it is OK in a MAC dev machine. Don't know why , same code , internet problem?

@Akryum
Copy link
Member

Akryum commented Mar 16, 2018

How much RAM do you have?

@colinfike
Copy link

I don't actually have the machine I was working on at the time but I believe I had 16gb with 8gb allocated to docker.

@maverickchangithub
Copy link

@Akryum now i have the same issue on a Mac dev machine too . I use 2048M ram in both machine , php 7.2 . Really strange issue , maybe it is my code which broke the tool , not confirmed yet.

i am using a laravel imap parser to parse gmail , and i am using vue for the front end , there is lot of problems now , but it shows the data , only cannot use vue-dev-tools to monitor the properties

@davidkhess
Copy link

davidkhess commented Jul 5, 2018

Seeing this problem also. @Akryum can we reopen this issue?

Does anybody know of a good work around?

@landart
Copy link

landart commented Jul 30, 2018

Still seeing the issue here. I'm on Chrome 65. 16GB RAM of which 2.9 available.

@lalmat
Copy link

lalmat commented Aug 6, 2018

Same problem here with a base64 (almost 100Ko) image in vue data. In my case, maybe a big data content should be truncated in data preview... But for an array, I've no idea.

@davidkhess
Copy link

davidkhess commented Sep 12, 2018

About the only workaround I've been able to come up with is to select the Vue component I need to inspect, wait for the error to pop up and then switch the display to Events.

At least that way I can inspect the Vue using $vm0 in the console.

@vcastro45
Copy link

I still seeing the issue too. Chrome 70, 16GB RAM, VueDevtools 4.1.5 beta

@davidkhess
Copy link

davidkhess commented Nov 28, 2018

@Akryum the folks at zalmoxisus/redux-devtools-extension fixed this problem like this:

https://github.com/zalmoxisus/redux-devtools-extension/pull/582/files

Seems that solution could be easily ported to vue-devtools?

@vcastro45
Copy link

Considering the @davidkhess 's answer and the problem that still be, is it possible to re-open the issue ? @Akryum

@smitt04
Copy link

smitt04 commented Jan 19, 2019

Why is this closed as it is still an issue? Please re-open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants