-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Crash in earcut #9148
Comments
Yes, looks like the same crash - although this was has a larger callstack, which is great. This is likely a bug in earcut - @bsudekum ideally you could either a) replicate with a debug build to get a line number and/or b) isolate the geometry that is causing this (hard, but maybe possible). |
Or the memory being passed to earcut is becoming invalid - which would likely be a mbgl bug. |
@brunoabinader - my understanding is that you were trying to isolate/fix this crash. Any progress? //cc @kkaefer |
We haven't been able to reproduce this issue again in the latest node release, have we @bsudekum? |
This seems very likely mapbox/earcut.hpp#54. Fix pending there. |
Wow, fantastic lead @mourner |
Hopefully fixed by #10251 |
As mentioned by @springmeyer - closing after #10251, we can reopen it if the issue reappears. |
Note, important part of this crash is in thread 1:
Starting to see this crash quite often. Looks similar to #9002
Note, this is using node-v3.5.3
/cc @tmpsantos @brunoabinader @kkaefer @springmeyer @jfirebaugh @mourner
The text was updated successfully, but these errors were encountered: