[Bug 463996] Review Request: tuxguitar - A multitrack tablature editor and player written in Java-SWT

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=463996





--- Comment #22 from Orcan Ogetbil <orcanbahri at yahoo.com>  2008-10-02 13:16:45 EDT ---
> * One more thing for misc/tuxguitar.sh
>  - The line 142 should be:
>----------------------------------------------------------------
>    exec ${JAVA} ${JAVA_FLAGS} ${PACKAGE_MAIN} $arg "$@"
>----------------------------------------------------------------
>    i.e. add exec to replace the called shell to java process.
FIXED

> * Freeze at the end

That happened to me once (when I was running tuxguitar with timidity and
openjdk) out of so many and I reported it to the author. See
http://www.tuxguitar.com.ar/forum/4/817/need-help-with-packaging-for-fedora/
Search for "OutOfMemoryError".

But I wasn't able to re-produce this. As I indicated in the above link we can
try playing with the stack sizes (the memory allocation for each thread,
indicated by "-Xms128m -Xmx128m" in the launching script). The author suggested
to increase them while google says decreasing might help.

I suggest switching to sun's java (no need to recompile, just use
"alternatives") and try to see if it will freeze again. If it doesn't then
there is a problem with openjdk and we need it to report to them.

We might be able to get more feedback once the package hits rawhide.

The updated files:
SRPM(F-8): http://6mata.com:8014/tuxguitar/tuxguitar-1.0-7.fc8.src.rpm
SRPM(F-9): http://6mata.com:8014/tuxguitar/tuxguitar-1.0-7.fc9.src.rpm
SPEC: http://6mata.com:8014/tuxguitar/tuxguitar.spec

%changelog
* Thu Oct 02 2008 Orcan Ogetbil <orcanbahri[AT]yahoo[DOT]com> - 1.0-7
- Added "exec" to replace the called shell to java process in the launching
script

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.