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.

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

Map maximum size exceeded #2988

Open
VolanDeVovan opened this issue Oct 2, 2024 · 2 comments
Open

Map maximum size exceeded #2988

VolanDeVovan opened this issue Oct 2, 2024 · 2 comments

Comments

@VolanDeVovan
Copy link

Describe the Bug

I use umami on a high traffic site
After a few days it stops working and spams with a message "Map maximum size exceeded"

This error was on older versions as well
It was not solved after updating to the current version

Screenshot_20241002_164608

Database

PostgreSQL

Relevant log output

RangeError: Map maximum size exceeded
    at Map.set (<anonymous>)
    at /app/node_modules/next/dist/server/lib/trace/tracer.js:134:45
    at NoopContextManager.with (/app/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:7062)
    at ContextAPI.with (/app/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:518)
    at NoopTracer.startActiveSpan (/app/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:18093)
    at ProxyTracer.startActiveSpan (/app/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:18854)
    at /app/node_modules/next/dist/server/lib/trace/tracer.js:122:103
    at NoopContextManager.with (/app/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:7062)
    at ContextAPI.with (/app/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:518)
    at NextTracerImpl.trace (/app/node_modules/next/dist/server/lib/trace/tracer.js:122:28)

Which Umami version are you using? (if relevant)

2.13.2

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

docker

@mikecao
Copy link
Collaborator

mikecao commented Oct 7, 2024

Where is this error coming from, the tracker or the UI?

@VolanDeVovan
Copy link
Author

Where is this error coming from, the tracker or the UI?

I got it from the docker compose logs
so I think it's a server error
Also it stopped writing new data and processing requests

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

No branches or pull requests

2 participants