Найти и исправить ошибку Next.js

Hi, I can look at the code, I have experience with testers, Docker, and generally with Next

Show original

Translate

Good afternoon.
I have experience, ready to help.
Send the code - we will cooperate.

Show original

Translate

I have experience optimizing Next.js/Node.js applications in production environments. In similar projects:

Identified bottlenecks in performance: memory leaks, long GC pauses.

Configured Docker containers with resource limits (--max-old-space-size for Node.js).

Conducted code audits and third-party libraries (e.g., overly "heavy" SSR, uncleared caches, improperly implemented render cycles).

Used monitoring tools (Node.js Profiler, clinic.js, pm2, top, docker stats) for resource consumption analysis.
…
Implemented caching optimizations, lazy loading, pagination for large databases (>100,000 products).

Show original

Translate

Hello, I would like to review the code to identify the cause of the error, most likely optimization is missing. We will agree on the time and price.

Show original

Translate

Hello
I can help fix the problem
The problem is not with the server but with the code or the site is allocated too little RAM (if anything, I'm not talking about the small amount of RAM on the server but about how much RAM the server will allocate for the site)
Write to me in private messages and I will help you

Show original

Translate

Hello Ablay,

I’ve reviewed the logs from your Next.js application, and the issue is clear:

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Your VPS has excellent resources (12 vCPUs, 48GB RAM), so the problem is likely inside the code — not the server.

What I’ll Do:
… Identify the memory leak or heavy operations causing the crash

Profile and optimize data fetching, especially if product pages load massive datasets

Ensure SSR/SSG logic is efficient (getStaticProps, getServerSideProps, or API routes)

Fix any full-page rendering of 400K+ products (pagination, lazy loading if missing)

Improve Docker and Node settings (--max-old-space-size, production flags)

Add performance logging and health monitoring

Deliverables:
Stable Next.js build (no memory crashes)

Improved product listing and rendering logic

Clean, optimized data flow (products, categories, filters)

Suggestions or fixes to avoid future bottlenecks


I've handled similar high-product-volume eCommerce apps and backend-heavy projects in Next.js + PostgreSQL/Mongo stacks and can confidently resolve this.

Please share access to your repo or Docker setup, and I can begin the diagnostics and repair.

Best regards,
Georgios Toutoudakis

Good afternoon, I have experience in development with Next.js and deployment on a server. Most likely, the problem is in the programmatically limited memory allocated for Next.

Show original

Translate

Hello. I have extensive experience with Next.js. Ready to collaborate

Show original

Translate