Skip to content

Issues: jerryscript-project/jerryscript

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

ecma_uint32_to_utf8_string did not fill string as zero-terminated. bug Undesired behaviour ecma core Related to core ECMA functionality
#5194 opened Dec 10, 2024 by lygstate
unit-doc-02.API-REFERENCE20.exe failed bug Undesired behaviour documentation Related to documentation test Related to testing windows Windows specific
#5191 opened Dec 9, 2024 by lygstate
Heap-buffer-overflow in lexer_construct_literal_object bug Undesired behaviour fuzzing Related to fuzz testing of the engine
#5189 opened Dec 8, 2024 by WS32bit
feature: Address performance issue and bugs about symbol and string by introduce atom ecma core Related to core ECMA functionality enhancement An improvement feature request Requested feature performance Affects performance
#5182 opened Nov 28, 2024 by lygstate
[Clang] Cannot build with pointer authentication (-mbranch-protection flag) bug Undesired behaviour tools Related to the tooling scripts
#5171 opened Nov 20, 2024 by bgergely0
Introduce 'ecma_is_value_nullish' ecma core Related to core ECMA functionality enhancement An improvement minor
#5170 opened Nov 19, 2024 by LaszloLango
SEGV in parser_stack_iterator_read_uint8 bug Undesired behaviour fuzzing Related to fuzz testing of the engine parser Related to the JavaScript parser
#5157 opened Aug 16, 2024 by Qbtly
SEGV in ecma_gc_free_native_pointer bug Undesired behaviour fuzzing Related to fuzz testing of the engine memory management Related to memory management or garbage collection
#5152 opened Aug 5, 2024 by Qbtly
global-buffer-overflow in scanner_literal_is_created bug Undesired behaviour fuzzing Related to fuzz testing of the engine parser Related to the JavaScript parser
#5151 opened Aug 5, 2024 by Qbtly
SEGV /jerryscript/jerry-core/parser/js/js-parser-expr.c:1997:11 in parser_parse_unary_expression bug Undesired behaviour fuzzing Related to fuzz testing of the engine parser Related to the JavaScript parser
#5150 opened Aug 5, 2024 by Qbtly
Assertion ECMA_STRING_IS_REF_EQUALS_TO_ONE (string_p) in ecma_free_string_list bug Undesired behaviour fuzzing Related to fuzz testing of the engine memory leak
#5135 opened Mar 26, 2024 by Qbtly
Heap-Buffer-Overflow in lexer_convert_ident_to_cesu8 /jerryscript/jerry-core/parser/js/js-lexer.c:2083:9 bug Undesired behaviour fuzzing Related to fuzz testing of the engine lexer Related to the tokenizer
#5134 opened Mar 26, 2024 by Qbtly
Assertion 'ecma_is_value_object (iter_result)' failed bug Undesired behaviour fuzzing Related to fuzz testing of the engine
#5118 opened Dec 1, 2023 by anbu1024
Assertion 'opts & PARSER_CLASS_LITERAL_CTOR_PRESENT' failed at /jerryscript/jerry-core/parser/js/js-parser-expr.c(parser_parse_class_body):538 bug Undesired behaviour fuzzing Related to fuzz testing of the engine parser Related to the JavaScript parser
#5113 opened Nov 23, 2023 by Qbtly
Segmentation Fault in release. Assertion 'context_p->source_p < context_p->source_end_p' failed in debug version bug Undesired behaviour fuzzing Related to fuzz testing of the engine lexer Related to the tokenizer
#5105 opened Oct 18, 2023 by anbu1024
Segmentation Fault in release. Assertion 'context_p->next_scanner_info_p->type == SCANNER_TYPE_FUNCTION' failed on debug. bug Undesired behaviour fuzzing Related to fuzz testing of the engine parser Related to the JavaScript parser
#5104 opened Oct 18, 2023 by anbu1024
Who to contact for security issues question Raised question
#5103 opened Oct 12, 2023 by psmoros
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.