Request: Chrome 4GB RAM Border

[ChristophPaulisch]

Dear Workiva support,

we now experienced an issue using Chrome (on Firefox it is working normally), which is occurring on huge documents, having many (big) concepts.

If you open the windows task manager and verify the Memory used for the chrome task , you will notice how it crashes after reaching the 4 GB border on our test example document.

So as Google (and Edge, as it also is based on chromium) is having this border officially for security reasons, we do not expect to change it from their side and therefore we address this to you, thought it is not your fault. In the end iXBRL documents can get very huge , from our experience on different customer , though we know US SEC reports are much smaller then our ESEF taxonomies in the EU.

Best Regards Christoph

[sagesmith-wf]

Can you include an example doc that triggers the failure for you?

[marckuipers]

Seems to be the same as this: https://github.com/Workiva/ixbrl-viewer/issues/358 Issue is caused by too many tags

[ChristophPaulisch]

Hello Mr. Smith,

sorry for the delay, i had to get the had to get the permission of the customer to share his file publicly, first. It's available now here:

https://sap-my.sharepoint.com/:u:/p/christoph_paulisch/EYU-IPaB2BlOjuJQq1baWWcBH_preJ_LddQ-9eptPNhUqA?e=9EGu6E

Best Regards Christoph

[sagesmith-wf]

@ChristophPaulisch I have done a bit of looking into this, I don't see a quick and easy solution on our side. I have noticed that the doc is 3GB in chrome when loaded even without the ixbrl-viewer and then the viewer attempts to add another 2GB. Even on small docs (1 fact) I have noticed about a 33% increase in the memory footprint which would push you over the limit (you are getting a 66% increase).

There are 415450 spans a lot with custom style tags in this document which is the reason why its taking up so much memory in chrome. If you were able to condense some of the spans on your side then I think you would be a lot closer to meeting the memory footprint. We are unlikely to get around to looking into this any further for the time being, but you are also welcome to PR a fix if you find anything out.

[ChristophPaulisch]

Hello Andrea,

now, i got a feedback from Workiva support.(see below) I will talk with my product owner about it ...

Regards Christoph

---

Von: sagesmith-wf @.> Gesendet: Montag, 23. Januar 2023 18:03 An: Workiva/ixbrl-viewer @.> Cc: Paulisch, Christoph @.>; Mention @.> Betreff: Re: [Workiva/ixbrl-viewer] Request: Chrome 4GB RAM Border (Issue #359)

Sie erhalten nicht oft eine E-Mail von @.*** Erfahren Sie, warum dies wichtig isthttps://aka.ms/LearnAboutSenderIdentification

@ChristophPaulischhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FChristophPaulisch&data=05%7C01%7Cchristoph.paulisch%40sap.com%7Cbc69acce2fdf4c2fa9e308dafd6c22b3%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638100938121332182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Mp1NwePK%2BdOH9iTNcw0xcM7dQVhAu3Qv3SBH5%2F442D4%3D&reserved=0 I have done a bit of looking into this, I don't see a quick and easy solution on our side. I have noticed that the doc is 3GB in chrome when loaded even without the ixbrl-viewer and then the viewer attempts to add another 2GB. Even on small docs (1 fact) I have noticed about a 33% increase in the memory footprint which would push you over the limit (you are getting a 66% increase).

There are 415450 spans a lot with custom style tags in this document which is the reason why its taking up so much memory in chrome. If you were able to condense some of the spans on your side then I think you would be a lot closer to meeting the memory footprint. We are unlikely to get around to looking into this any further for the time being, but you are also welcome to PR a fix if you find anything out.

— Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWorkiva%2Fixbrl-viewer%2Fissues%2F359%23issuecomment-1400757942&data=05%7C01%7Cchristoph.paulisch%40sap.com%7Cbc69acce2fdf4c2fa9e308dafd6c22b3%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638100938121332182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HOdiwdLH66Qfyz57F1y3N63F4eLQdl%2B1IqokTopLAGA%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA5GZVNAK76R2S2G4DI42B33WT3BXDANCNFSM6AAAAAATZCG26Q&data=05%7C01%7Cchristoph.paulisch%40sap.com%7Cbc69acce2fdf4c2fa9e308dafd6c22b3%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638100938121332182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ewYjzfT2%2B3GAbheUwssL1T89R1OjRkOKJcbStjxd8vw%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>

[ChristophPaulisch]

Hello Christoph, thanks for your reply. If you need some information from me or a call, please contact me.

Regards,

Andrea Migliore

Manager | M. +39 3401949848 | @.*** <$mailPrimary>

qintesi.com https://www.qintesi.com/

[image: Qintesi] [image: Qintesi] https://www.repubblica.it/dossier/economia/qualita-e-mercati/2021/03/22/news/itqf_analizza_da_20_anni_le_aziende_top_in_europa-289892136/

Milano | Marcon | Roma | Bergamo - HQ

This e-mail message, including any attachment, is intended only for the named recipients. Unauthorized individuals are not permitted access to this information. Any dissemination, distribution, disclosure or copying of this information is unauthorized and strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail and delete this message and any attachment.

Il giorno mar 24 gen 2023 alle ore 09:35 Paulisch, Christoph < @.***> ha scritto:

Hello Andrea,

now, i got a feedback from Workiva support.(see below) I will talk with my product owner about it ...

Regards Christoph

Von: sagesmith-wf @.> Gesendet: Montag, 23. Januar 2023 18:03 An: Workiva/ixbrl-viewer @.> Cc: Paulisch, Christoph @.>; Mention < @.> Betreff: Re: [Workiva/ixbrl-viewer] Request: Chrome 4GB RAM Border (Issue #359)

Sie erhalten nicht oft eine E-Mail von @.*** Erfahren Sie, warum dies wichtig ist https://aka.ms/LearnAboutSenderIdentification

@ChristophPaulisch https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FChristophPaulisch&data=05%7C01%7Cchristoph.paulisch%40sap.com%7Cbc69acce2fdf4c2fa9e308dafd6c22b3%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638100938121332182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Mp1NwePK%2BdOH9iTNcw0xcM7dQVhAu3Qv3SBH5%2F442D4%3D&reserved=0 I have done a bit of looking into this, I don't see a quick and easy solution on our side. I have noticed that the doc is 3GB in chrome when loaded even without the ixbrl-viewer and then the viewer attempts to add another 2GB. Even on small docs (1 fact) I have noticed about a 33% increase in the memory footprint which would push you over the limit (you are getting a 66% increase).

There are 415450 spans a lot with custom style tags in this document which is the reason why its taking up so much memory in chrome. If you were able to condense some of the spans on your side then I think you would be a lot closer to meeting the memory footprint. We are unlikely to get around to looking into this any further for the time being, but you are also welcome to PR a fix if you find anything out.

— Reply to this email directly, view it on GitHub https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWorkiva%2Fixbrl-viewer%2Fissues%2F359%23issuecomment-1400757942&data=05%7C01%7Cchristoph.paulisch%40sap.com%7Cbc69acce2fdf4c2fa9e308dafd6c22b3%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638100938121332182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HOdiwdLH66Qfyz57F1y3N63F4eLQdl%2B1IqokTopLAGA%3D&reserved=0, or unsubscribe https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA5GZVNAK76R2S2G4DI42B33WT3BXDANCNFSM6AAAAAATZCG26Q&data=05%7C01%7Cchristoph.paulisch%40sap.com%7Cbc69acce2fdf4c2fa9e308dafd6c22b3%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638100938121332182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ewYjzfT2%2B3GAbheUwssL1T89R1OjRkOKJcbStjxd8vw%3D&reserved=0 . You are receiving this because you were mentioned.Message ID: @.***>

[sagesmith-wf]

@ChristophPaulisch, just as an FYI I see:

This e-mail message, including any attachment, is intended only for the named recipients. Unauthorized individuals are not permitted access to this information. Any dissemination, distribution, disclosure or copying of this information is unauthorized and strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail and delete this message and any attachment.

And this is now available to everyone in the world with internet access.

[sagesmith-wf]

The document doesn't leave enough space for the ixbrl-viewer to generate as stated here closing for now