On Mon, Mar 4, 2024 at 2:54 PM Angelo Dell'Aera <angelo.della...@gmail.com> wrote: > > Hi all, > starting from a few weeks I started observing these crashes while using the > Python > wrapper STPyV8 [1]. I am the lead developer of STPyV8 and no relevant changes > were > introduced recently other than updating the V8 version to use in the building > process. > This trace was generated using V8 12.2.281.19 > > <--- Last few GCs ---> > > [380775:0x17d0000] 254778 ms: Scavenge 75.3 (80.3) -> 73.4 (80.3) MB, > pooled: 0 MB, 0.31 / 0.00 ms (average mu = 1.000, current mu = 1.000) > allocation failure; > [380775:0x17d0000] 254783 ms: Scavenge 75.3 (80.3) -> 73.4 (80.3) MB, > pooled: 0 MB, 0.31 / 0.00 ms (average mu = 1.000, current mu = 1.000) > allocation failure; > [380775:0x17d0000] 265747 ms: Scavenge 76.3 (81.5) -> 75.1 (79.0) MB, > pooled: 2 MB, 0.88 / 0.05 ms (average mu = 1.000, current mu = 1.000) > allocation failure; > > > <--- JS stacktrace ---> > > > > # > # Fatal process out of memory: DateTimePatternGeneratorCache::CreateGenerator > # > ==== C stack trace =============================== > > > /opt/env/lib/python3.9/site-packages/_STPyV8.cpython-39-x86_64-linux-gnu.so(v8::base::debug::StackTrace::StackTrace()+0x13) > [0x7f7d3ef16503] > > /opt/env/lib/python3.9/site-packages/_STPyV8.cpython-39-x86_64-linux-gnu.so(+0xcf419b) > [0x7f7d3ef1819b] > > /opt/env/lib/python3.9/site-packages/_STPyV8.cpython-39-x86_64-linux-gnu.so(v8::base::FatalOOM(v8::base::OOMType, > char const*)+0x38) [0x7f7d3f879f68] > > /opt/env/lib/python3.9/site-packages/_STPyV8.cpython-39-x86_64-linux-gnu.so(v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, > char const*, v8::OOMDetails const&)+0x2ac) [0x7f7d3ef1b58c] > > /opt/env/lib/python3.9/site-packages/_STPyV8.cpython-39-x86_64-linux-gnu.so(+0xfe498a) > [0x7f7d3f20898a] > > /opt/env/lib/python3.9/site-packages/_STPyV8.cpython-39-x86_64-linux-gnu.so(v8::internal::JSDateTimeFormat::CreateDateTimeFormat(v8::internal::Isolate*, > v8::internal::Handle<v8::internal::Map>, > v8::internal::Handle<v8::internal::Object>, > v8::internal::Handle<v8::internal::Object>, > v8::internal::JSDateTimeFormat::RequiredOption, > v8::internal::JSDateTimeFormat::DefaultsOption, char const*)+0x8b6) > [0x7f7d3f206e06] > > /opt/env/lib/python3.9/site-packages/_STPyV8.cpython-39-x86_64-linux-gnu.so(v8::internal::JSDateTimeFormat::New(v8::internal::Isolate*, > v8::internal::Handle<v8::internal::Map>, > v8::internal::Handle<v8::internal::Object>, > v8::internal::Handle<v8::internal::Object>, char const*)+0x1a) > [0x7f7d3f207efa] > > /opt/env/lib/python3.9/site-packages/_STPyV8.cpython-39-x86_64-linux-gnu.so(v8::internal::Builtin_DateTimeFormatConstructor(int, > unsigned long*, v8::internal::Isolate*)+0xfe) [0x7f7d3f8bed4e] > > /opt/env/lib/python3.9/site-packages/_STPyV8.cpython-39-x86_64-linux-gnu.so(+0x151e5b6) > [0x7f7d3f7425b6] > > Regards, > Angelo > > [1] https://github.com/cloudflare/stpyv8
Did you also update ICU? That error message indicates V8 couldn't create a icu::DateTimePatternGenerator instance. Try building V8 with debug checks enabled, that should give you a better idea of the root cause. -- -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/CAHQurc-FZ6ftaRTv%2BegPw3j3yk2w1oi%3Dd8ZH8AOwJHbE8hsrCw%40mail.gmail.com.
