felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-729) Shell-TUI causes 100% CPU load when using javaw launcher
Date Tue, 31 Mar 2009 14:52:55 GMT

     [ https://issues.apache.org/jira/browse/FELIX-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Karl Pauls updated FELIX-729:

    Fix Version/s: shell-1.2.0

> Shell-TUI causes 100% CPU load when using javaw launcher
> --------------------------------------------------------
>                 Key: FELIX-729
>                 URL: https://issues.apache.org/jira/browse/FELIX-729
>             Project: Felix
>          Issue Type: Bug
>          Components: Shell
>    Affects Versions: felix-1.0.4, felix-1.2.0
>         Environment: Windows 2000 SP4, Windows Vista Enterprise, JDK 1.6
>            Reporter: Barend Garvelink
>            Assignee: Richard S. Hall
>             Fix For: shell-1.2.0
> I ran into this issue at work with Felix 1.0.4 on Win2k SP4 and reproduced it at home
with Felix 1.2.1 on Vista Enterprise, both on JDK 1.6. I only discovered it by accident, as
I normally use the console during development. I suspect the people reading this do, too :-).
> When using the javaw.exe launcher rather than the java.exe launcher, Felix-shell-TUI
permanently draws 100% CPU (divide by the number of cores, home PC reports 50%). After removing
shell-TUI from the autostart list, Felix can be run with the javaw launcher without issue,
demonstrating that the problem originates from that bundle.
> Steps to reproduce:
> 1)  unzip a fresh copy of Felix-1.2.1.zip
> 2)  in the install dir, create two batch files: felix-console.bat and felix-noconsole.bat,
one executes `java -Dfelix.cache.profile=consoletest -jar bin\felix.jar`, the other executes
`javaw -Dfelix.cache.profile=consoletest -jar bin\felix.jar`
> 3) double-click either from Windows Explorer, note that when you run the "javaw" one,
CPU shoots to 100% and stays there.
> Running them from within Windows Explorer isn't strictly necessary to reproduce the issue,
the problem will also show when you start the batch file from the command line.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message