When using amuttsch's final version of OPAL (commit b8d1adc "Add EagerTAC performance evaluation"), one does not get determinstic results for
runMain org.opalj.support.info.Purity -JDK
even if heap speace is increased.
To find a possible RA bug, branch fix/removeCellAftercheckThisWithOPAL has been created, but neither this branch nor any of the following commits of RA have lead to determinstic results:
ee939
d17e4f8 (performance/pull HEAD)
bff7f3
23733
Both for these negativ results and the fact that RA tests do not fail, it is likely, that the bug is on OPAL's side, e.g. the ReactiveAsyncPropertyStore or the PurityAnalysis itself. (The latter is less likely, because the analysis seems to work for the standard PropertyStore.)
When using amuttsch's final version of OPAL (commit b8d1adc "Add EagerTAC performance evaluation"), one does not get determinstic results for
runMain org.opalj.support.info.Purity -JDKeven if heap speace is increased.
To find a possible RA bug, branch fix/removeCellAftercheckThisWithOPAL has been created, but neither this branch nor any of the following commits of RA have lead to determinstic results:
ee939
d17e4f8 (performance/pull HEAD)
bff7f3
23733
Both for these negativ results and the fact that RA tests do not fail, it is likely, that the bug is on OPAL's side, e.g. the ReactiveAsyncPropertyStore or the PurityAnalysis itself. (The latter is less likely, because the analysis seems to work for the standard PropertyStore.)