nccgroup/aws-inventory

Message length exceeded maximum allowed length.

imtpalmer opened this issue · 2 comments

imtpalmer commented

Description:

Selecting the inventory file on the main page, once the file is loaded, I clicked on the "inventory" tab and a "loading" message is displayed. When I open the developer tools in the browser, the below error is displayed. The "loading" message runs forever...

content-script.js:17 Uncaught TypeError: Error in invocation of runtime.sendMessage(optional string extensionId, any message, optional object options, optional function responseCallback): Message length exceeded maximum allowed length.
    at content-script.js:17
(anonymous) @ content-script.js:17
postMessage (async)
l @ installHook.js:1
window.__REACT_DEVTOOLS_GLOBAL_HOOK__.e.version.t.onCommitFiberRoot @ installHook.js:1
(anonymous) @ main.a4beb15c.js:43472
(anonymous) @ main.a4beb15c.js:43472
$t @ main.a4beb15c.js:43472
fr @ main.a4beb15c.js:43472
dr @ main.a4beb15c.js:43472
lr @ main.a4beb15c.js:43472
sr @ main.a4beb15c.js:43472
or @ main.a4beb15c.js:43472
Zn @ main.a4beb15c.js:43472
enqueueSetState @ main.a4beb15c.js:43472
(anonymous) @ main.a4beb15c.js:43472
(anonymous) @ main.a4beb15c.js:43472
(anonymous) @ main.a4beb15c.js:43472
load (async)
(anonymous) @ main.a4beb15c.js:43472
o @ main.a4beb15c.js:43472
invokeGuardedCallback @ main.a4beb15c.js:43472
invokeGuardedCallbackAndCatchFirstError @ main.a4beb15c.js:43472
u @ main.a4beb15c.js:43472
p @ main.a4beb15c.js:43472
m @ main.a4beb15c.js:43472
f @ main.a4beb15c.js:43472
v @ main.a4beb15c.js:43472
y @ main.a4beb15c.js:43472
He @ main.a4beb15c.js:43472
gr @ main.a4beb15c.js:43472
J @ main.a4beb15c.js:43472
We @ main.a4beb15c.js:43472

The inventory JSON file is > 300 MB

Desktop (please complete the following information):

  • OS: Mac OS X
  • Python Version (python -V): 3.7
  • Commandline used to run tool: python aws_inventory.py
  • Version (aws_inventory.py -V): [e.g. 0.1.1]

Additional context
Add any other context about the problem here. Browser and version?

bitsandsalsa commented

I think you might be hitting a limitation of the tool due to its current design of reading in a potentially (very) large data file. Aside from changing the design, you could try adding some filters when doing the initial scan so the data file size is smaller.

ncc-erik-steringer commented

Hi there, did the response from bitsandsalsa help resolve this issue?