You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This then repeats for a long time and eventually crashes in alloc::vec::Vec<T>::with_capacity (mod.rs:483) and finally in jemalloc. Its a bit weird that we get a SIGSEGV / SEGV_ACCERR instead of an allocation panic, but here we are 🤷🏻♂️
I wasn’t able yet to figure out what symbol is causing this however.
Though I remember I was suggesting a general recursion / memory usage limit that is being checked for so that we do not run into things like this.
The text was updated successfully, but these errors were encountered:
It looks like we get some new customer pdb files that exhibit some infinite / mutual recursion that looks like this:
This then repeats for a long time and eventually crashes in
alloc::vec::Vec<T>::with_capacity (mod.rs:483)
and finally in jemalloc. Its a bit weird that we get aSIGSEGV / SEGV_ACCERR
instead of an allocation panic, but here we are 🤷🏻♂️I wasn’t able yet to figure out what symbol is causing this however.
Though I remember I was suggesting a general recursion / memory usage limit that is being checked for so that we do not run into things like this.
The text was updated successfully, but these errors were encountered: