Project

General

Profile

Bug #8929

Constructors with EXTENT parameters fails

Added by Marian Edu about 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Marian Edu about 2 years ago

We have this issue with JsonArray that takes extent parameters as input in constructor, instantiation fails for any of these and the cause seems to be from resolveLegacyEntry method, at some point when extent is used it checks if the sigType.isArray (line 5678 in trunk) but that can never be true because calculateType resolves class array to it's component type already.

Also, for whatever reason, we've got cached keys with null method that leads to NPE in ControlFlowOps.getCache method, switching mthd with value.method when calling equals or using Objects.equals instead solves the issue.

As far as I can see those issues are still present in trunk, although the method resolve was considerably changed so we're just applying local fixes on #6410b but those will most probably need to be fixed in trunk as well.

Also available in: Atom PDF