[
https://issues.apache.org/jira/browse/FELIX-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676664#action_12676664
]
Richard S. Hall commented on FELIX-961:
---------------------------------------
It is certainly a known issue that finding a consistent class space may take a
long time, since the algorithm is very simplistic and the search space is
potentially very big. It should not hang or loop indefinitely, however. If it
is, that sounds like a bug.
> 100% CPU looping inside uses calculation
> ----------------------------------------
>
> Key: FELIX-961
> URL: https://issues.apache.org/jira/browse/FELIX-961
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: felix-1.4.1
> Reporter: Stuart McCulloch
> Attachments: USES_TESTCASE.zip, USES_TESTCASE2.zip
>
>
> While investigating a problem report against pax-runner
> (http://article.gmane.org/gmane.comp.java.ops4j.general/6778) I found it was
> actually caused by a 100% CPU loop inside the "uses" calculation code. In
> Felix 1.4.1 this was stopping the shell bundle from activating, hence the
> lack of console. Using the trunk build I can get a console, but the looping
> still occurs with the testcase.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
