Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P4
Fix Version/s: 9
Affects Version/s: None
Component/s: security-libs
Labels:
- CPU18_07-critical-SQE-reject
- CPU18_07-critical-reject

Resolved In Build:
b142
OS:

windows

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8208948	8u201	Ivan Gerasimov	P4	Resolved	Fixed	b01
JDK-8199491	8u192	Ivan Gerasimov	P4	Resolved	Fixed	b01
JDK-8216849	emb-8u201	Ivan Gerasimov	P4	Resolved	Fixed	master
JDK-8199508	7u201	Ivan Gerasimov	P4	Resolved	Fixed	b01
JDK-8219287	openjdk7u	Ivan Gerasimov	P4	Resolved	Fixed	master
JDK-8199582	6u211	Ivan Gerasimov	P4	Resolved	Fixed	b01

Currently, the form of ::operator new() is used, which throws std::bad_alloc upon failure.
Since we don't have handling of c++ exceptions in the code, such failures wouldn't be handled.

Instead, ::operator new(std::nothrow) can be used, which would return 0 in a case of a failure.
Then we can (try to) throw Java exception of type OutOfMemoryError.

backported by

JDK-8199491 Native implementation of sunmscapi should use operator new (nothrow) for allocations

Resolved

JDK-8199508 Native implementation of sunmscapi should use operator new (nothrow) for allocations

Resolved

JDK-8199582 Native implementation of sunmscapi should use operator new (nothrow) for allocations

Resolved

JDK-8208948 Native implementation of sunmscapi should use operator new (nothrow) for allocations

Resolved

JDK-8216849 Native implementation of sunmscapi should use operator new (nothrow) for allocations

Resolved

JDK-8219287 Native implementation of sunmscapi should use operator new (nothrow) for allocations

Resolved

links to

Review

(1 backported by, 1 links to)

Assignee:: Ivan Gerasimov

Reporter:: Ivan Gerasimov

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2016-09-05 12:31

Updated:: 2019-02-18 13:40

Resolved:: 2016-10-22 07:05

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates