Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

SVG processing limit(s) ?

  • 1 Antwort
  • 0 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von mvgulik

mvgulik
mvgulik
more options

Related to some personal SVG project files. Which are relative large files (containing lots of generated paths and other data).

On the largest of these files I spotted that some general svg-viewer failed with a "XML parse error: cannot load more than 200.000 XML elements" error message.

The same file, when viewed in Firefox (114~, Linux, Mint), also developed some odd hiccup that did not make sense. Unless ...

Is there a similar limitation active in Firefox ?

- I tried to see if "Inspect>Console" gave some potential related message on this. But spotted nothing out of the ordinary. - Searched developer.mozilla.org for any related svg data. But could not find any. - After ditching some data in the effected file, unrelated to the hiccup part, the hiccup disappeared. Suggesting I did hit some svg limit in Firefox. - File size: ~26.5MB. Number of elements: Other than more than 200.000, unknown at this point. (not sure how to count them at this moment either)

Related to some personal SVG project files. Which are relative large files (containing lots of generated paths and other data). On the largest of these files I spotted that some general svg-viewer failed with a "XML parse error: cannot load more than 200.000 XML elements" error message. The same file, when viewed in Firefox (114~, Linux, Mint), also developed some odd hiccup that did not make sense. Unless ... Is there a similar limitation active in Firefox ? - I tried to see if "Inspect>Console" gave some potential related message on this. But spotted nothing out of the ordinary. - Searched developer.mozilla.org for any related svg data. But could not find any. - After ditching some data in the effected file, unrelated to the hiccup part, the hiccup disappeared. Suggesting I did hit some svg limit in Firefox. - File size: ~26.5MB. Number of elements: Other than more than 200.000, unknown at this point. (''not sure how to count them at this moment either'')

Ausgewählte Lösung

Idea take time. And on a hunch of what else might have triggered the hiccup. I could quickly reproduce the hiccup in the stripped down version (~15MB). Ergo: It can't be related to some svg limit. (Seem I have a class-naming collision to blame in this case.)

Sorry.

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (1)

mvgulik
mvgulik Fragesteller
more options

Ausgewählte Lösung

Idea take time. And on a hunch of what else might have triggered the hiccup. I could quickly reproduce the hiccup in the stripped down version (~15MB). Ergo: It can't be related to some svg limit. (Seem I have a class-naming collision to blame in this case.)

Sorry.