-
-
Notifications
You must be signed in to change notification settings - Fork 33.9k
Closed
Closed
Copy link
Labels
i18n-apiIssues and PRs related to the i18n implementation.Issues and PRs related to the i18n implementation.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.vmIssues and PRs related to the vm subsystem.Issues and PRs related to the vm subsystem.
Description
- Version: 8.4.0
- Platform: Linux 4.9.0-3-amd64 deps: update openssl to 1.0.1j #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06) x86_64 GNU/Linux
- Subsystem: v8, vm, intl
#3111 / #4253 fixed this in the main context, but the bug applies to VM contexts too unfortunately.
$ node -p "vm.runInNewContext('new Intl.v8BreakIterator()')"
#
# Fatal error in , line 0
# Failed to create ICU break iterator, are ICU data files missing?
#
==== C stack trace ===============================
node(v8::base::debug::StackTrace::StackTrace()+0x16) [0x15c8c36]
node() [0x1451857]
node(V8_Fatal+0xd8) [0x15c3998]
node() [0x1116487]
node(v8::internal::Runtime_CreateBreakIterator(int, v8::internal::Object**, v8::internal::Isolate*)+0x170) [0x1200a40]
[0x1ec0a1974998]
Illegal instruction
Offending line:
node/deps/v8/src/objects/intl-objects.cc
Line 879 in d15a5c0
| FATAL("Failed to create ICU break iterator, are ICU data files missing?"); |
At this point I'm thinking of just including the data files needed for the break iterator to work even if it's not part of the ECMA-402 spec yet.
/cc @nodejs/intl @srl295
Metadata
Metadata
Assignees
Labels
i18n-apiIssues and PRs related to the i18n implementation.Issues and PRs related to the i18n implementation.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.vmIssues and PRs related to the vm subsystem.Issues and PRs related to the vm subsystem.