Fatal RangeError: Maximum call stack size exceeded occurred within Mapbox GL JS.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
Hi there, I am getting the following error with mapbox on client devices.
The error can be seen at the following public Sentry url: https://of-interest.sentry.io/share/issue/a0a0d1afa40548fba70194e6fb604a3f/
This is most likely a bug, please report this via https://github.com/mapbox/mapbox-gl-js/issues/new?assignees=&labels=&template=Bug_report.md
and paste the contents of this message in the report.
Thank you!
Filter Expression:
${JSON.stringify(a,null,2)}
{snip} 1,this.supportsFog=!1,this.supportsFreeCamera=!1,this.zAxisUnit="meters",this.isReprojectedInTileSpace=!0,this.unsupportedLayers=["custom"], {snip}
{snip} bient_directional_factor=mix(directional_factor_min,1.0,min((NdotL+1.0),1.0));const float vertical_factor_min=0.92;float vertical_factor=mix {snip}
#ifndef HAS_UNIFORM_u_${a}
in ${r} ${i} ${a};
#else
uniform ${r} ${i} u_${a};
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Sentry report and the captured Filter Expression in the issue body, then trace where that expression is processed in Mapbox GL JS. Confirm a reproducible client-side case and identify the path causing the RangeError; done means the failure is explained and a verified fix or regression test covers it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100