Vuze shutting down as soon as opened - How to export Crash dump list on mac?

[1914]

Hi all. 
Vuze keeps shutting down as soon as it is opened.
I have read through various other threads regarding the same problem, and it seems I need to export a crash dump list to assist with troubleshooting. 
However, I am using Vuze on a Mac, and I cannot find out how to do this. I have looked through the forums and done some google searches, and cannot find how to export the crash dump list on a Mac version. 
So :
- How to export Crash dump list on mac?

I am running Vuze 5.7.3 on Mountain Lion, but the computer has good specs (16gb RAM etc). 

Thanks for any assistance

[parg]

Is this new behaviour or a fresh install? If new, did you grab the Java 8 version of Vuze over the legacy Apple-Java 1.6?

You could open up the console on the mac and see if there's any logs there.

[1914]

Hi Parg .

It is intermittent behaviour (by which I mean : It is happening every time I open Vuze at the moment, and in the past it has happened). So it MIGHT be related to some Vuze updates (probably).
When it has happened in the past, I have waited for the next Vuze update, or downgraded, and this has sometimes fixed the issue.

However I am not 100% certain if it is related, because Vuze is set to automatically update,
and I only ever check my version when I have problems !(I'm not sure if I have logs of such updates on my system).
 I could try downgrading to previous version I suppose. The only other thing I can think which it may be related to is too many files in the library, as I suspect this may have been a problem in the past ;However, I have done a big clean out of my Vuze library of old files, and checked the maximum simultaneous DL and ULs in the queue, and they are set at 20 each or 30 total DLs+ULs max .
Therefore , the queue should be no issue (as in the past, I have allowed greater numbers without issue.)I tried smaller numbers too, which was no help.
 I'm not too sure if this is the information you require from the console,but I opened console and typed "Vuze" into the filter / search box (after opening Vuze and it closing)and got the following :

25/10/16 10:41:10.000 AM kernel[0]: Sandbox: mdworker(24489) deny file-read-data /Users/Shared/Library/Application Support/Vuze
25/10/16 10:41:10.000 AM kernel[0]: Sandbox: mdworker(24489) deny file-read-data /Users/Shared/Library/Application Support/Vuze/Resources
25/10/16 10:45:03.565 AM WindowServer[101]: CGXDisableUpdate: UI updates were forcibly disabled by application "Vuze" for over 1.00 seconds. Server has re-enabled them.
25/10/16 10:45:03.618 AM WindowServer[101]: reenable_update_for_connection: UI updates were finally reenabled by application "Vuze" after 1.05 seconds (server forcibly re-enabled them after 1.00 seconds)
25/10/16 10:45:26.501 AM WindowServer[101]: CGXDisableUpdate: UI updates were forcibly disabled by application "Vuze" for over 1.00 seconds. Server has re-enabled them.
25/10/16 10:45:26.689 AM WindowServer[101]: reenable_update_for_connection: UI updates were finally reenabled by application "Vuze" after 1.19 seconds (server forcibly re-enabled them after 1.00 seconds)
25/10/16 10:45:30.016 AM WindowServer[101]: CGXDisableUpdate: UI updates were forcibly disabled by application "Vuze" for over 1.00 seconds. Server has re-enabled them.
25/10/16 10:45:31.331 AM WindowServer[101]: reenable_update_for_connection: UI updates were finally reenabled by application "Vuze" after 2.31 seconds (server forcibly re-enabled them after 1.00 seconds)
25/10/16 10:45:34.959 AM WindowServer[101]: CGXDisableUpdate: UI updates were forcibly disabled by application "Vuze" for over 1.00 seconds. Server has re-enabled them.
25/10/16 10:45:35.232 AM WindowServer[101]: reenable_update_for_connection: UI updates were finally reenabled by application "Vuze" after 1.27 seconds (server forcibly re-enabled them after 1.00 seconds)
25/10/16 10:45:37.346 AM WindowServer[101]: CGXDisableUpdate: UI updates were forcibly disabled by application "Vuze" for over 1.00 seconds. Server has re-enabled them.
25/10/16 10:45:40.316 AM WindowServer[101]: reenable_update_for_connection: UI updates were finally reenabled by application "Vuze" after 3.97 seconds (server forcibly re-enabled them after 1.00 seconds)
25/10/16 10:45:45.103 AM WindowServer[101]: CGXDisableUpdate: UI updates were forcibly disabled by application "Vuze" for over 1.00 seconds. Server has re-enabled them.
25/10/16 10:45:45.113 AM WindowServer[101]: reenable_update_for_connection: UI updates were finally reenabled by application "Vuze" after 1.01 seconds (server forcibly re-enabled them after 1.00 seconds)
25/10/16 10:45:51.954 AM WindowServer[101]: CGXDisableUpdate: UI updates were forcibly disabled by application "Vuze" for over 1.00 seconds. Server has re-enabled them.
25/10/16 10:45:56.093 AM WindowServer[101]: reenable_update_for_connection: UI updates were finally reenabled by application "Vuze" after 5.14 seconds (server forcibly re-enabled them after 1.00 seconds)
25/10/16 10:46:06.839 AM WindowServer[101]: CGXDisableUpdate: UI updates were forcibly disabled by application "Vuze" for over 1.00 seconds. Server has re-enabled them.
25/10/16 10:46:20.840 AM WindowServer[101]: disable_update_likely_unbalanced: UI updates still disabled by application "Vuze" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
25/10/16 10:46:49.682 AM WindowServer[101]: reenable_update_for_connection: UI updates were finally reenabled by application "Vuze" after 43.85 seconds (server forcibly re-enabled them after 1.00 seconds)
 
.........

Thanks !

[parg]

Hmm, nothing obvious there - no idea what that 'deny file-read-data' is, Vuze needs access to those folders but I'm not sure what the sandbox thread is, might be something else.

How many torrents do you think you have in your Vuze library? 1000s? Large numbers can cause issues with Java memory exhaustion but a few hundred is usually OK as long as they're not all active (which is true with your settings)

What version of Java is Vuze using? It says in the 'About' details. Also, if you can get Vuze to run for long enough you could try and generate a debug.zip file (Help menu, last option). Alternatively you could zip up the 'logs' folder in the Azureus config folder and send them over to paul@vuze.com

Thanks!

[1914]

(Oops, I thought I posted this already !)

I can open Vuze long enough to check these things.
It stays open for about a minute or two,
and then my computer fans go on high-speed as if overheating.
This continues a bit, and then I get the "spinning beach ball of doom".
At this point, I have to force quit vuze, or it manages to quit itself sometimes after a few minutes of this.

I have :
279 files in downloads (seeding a few : 20 max at any same time).
597 waiting to be downloaded (but nearly all of these are paused / stopped. I only ever unpause 10 or 20 at a time).
.................

Java version :
According to selecting
Vuze --> About -->

Java 1.8.0_92 (64 bit)
Oracle Corporation
SWT v4528, cocoa
Mac OS X v10.8.5, x86_64
V5.7.3.0/4 az3

.................
Vuze does stay open long enough for me to do a few things , so :
I found the debug.zip under help, and have just generated a file and sent it to paul@vuze.com.

Thanks very much again for your help Parg (:

[parg]

You're running out of Java VM memory - check the 'debug.log' file and you'll see lots of 

java.lang.OutOfMemoryError: GC overhead limit exceeded

Try increasing the JVM size to (say) 512MB - see http://wiki.vuze.com/w/Java_VM_memory_usage

You need to edit the info.plist file to do this

[1914]

Hi Parg.Thanks again for your help!I am trying to edit these settings.I am in the info.plist file, using X-Code.Under the JavaVM list file, it has the following list in T The instructions from the link you sent seem to end the details after the list file is open.
"On Mac OSX you will need to modify the Info.plist file within Vuze.app: Right-click Vuze app in /Applications/ folder and select Show Package Contents, then open the Contents/Info.plist file in TextEdit. You can modify the existing VMOptions value string as desired."..............I am GUESSING I am supposed to edit this line  / string ??

<string>-Xmx256m</string>

??But I am unsure. I have no experience in Java language / programming . ..................
 FULL LIST FILE.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist SYSTEM "file://localhost/System/Library/DTDs/PropertyList.dtd">
<plist version="0.9">
<dict>
<key>CFBundleName</key>
<string>Vuze</string>
<key>CFBundleExecutable</key>
<string>JavaApplicationStub</string>
<key>CFBundleIconFile</key>
<string>app.icns</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleIdentifier</key>
<string>com.azureus.vuze</string>
<key>CFBundleVersion</key>
<string>5.7.3.0</string>
<key>CFBundleShortVersionString</key>
<string>5.7.3.0</string>
<key>CFBundleGetInfoString</key>
<string>5.7.3.0</string>
<key>CFBundleDevelopmentRegion</key>
<string>en</string>
<key>CFBundleAllowMixedLocalizations</key>
<true/>
<key>NSHighResolutionCapable</key>
<true/>
<key>LSHasLocalizedDisplayName</key>
<true/>
<key>CFBundleDocumentTypes</key>
<array>
    <dict>
        <key>LSHandlerRank</key>
        <string>Owner</string>
        <key>CFBundleTypeExtensions</key>
        <array>
            <string>torrent</string>
            <string>tor</string>
            <string>vuze</string>
            <string>vuz</string>
            <string>bctpuri</string>
        </array>
        <key>CFBundleTypeIconFile</key>
        <string>app.icns</string>
        <key>CFBundleTypeMIMETypes</key>
        <array>
            <string>application/x-bittorrent</string>
            <string>application/x-bctp-uri</string>
            <string>application/x-bc-uri</string>
            <string>application/x-vuze</string>
        </array>
        <key>CFBundleTypeName</key>
        <string>Vuze Download</string>
        <key>CFBundleTypeOSTypes</key>
        <array>
            <string>TORR</string>
        </array>
        <key>CFBundleTypeRole</key>
        <string>Editor</string>
    </dict>
</array>
<key>CFBundleURLTypes</key>
<array>
    <dict>
        <key>CFBundleURLName</key>
        <string>magnet url</string>
        <key>CFBundleURLSchemes</key>
        <array>
            <string>magnet</string>
            <string>dht</string>
            <string>vuze</string>
            <string>bc</string>
            <string>bctp</string>
        </array>
    </dict>
</array>
<key>NSHighResolutionCapable</key>
<true/>
<key>NSAppTransportSecurity</key>
<dict>
    <key>NSExceptionDomains</key>
    <dict>
        <key>vuze.com</key>
        <dict>
            <key>NSIncludesSubdomains</key>
            <true/>
            <key>NSExceptionAllowsInsecureHTTPLoads</key>
            <true/>
        </dict>
    </dict>
    <key>NSAllowsArbitraryLoads</key>
    <true/>
</dict>
<!-- I4J_INSERT_DOCTYPE -->
<key>i4j.baseDir</key>
<string>$APP_PACKAGE/../</string>
<key>LSMinimumSystemVersion</key>
<string>10.7.3</string>
<key>i4j.appId</key>
<string>8461-7759-5462-8226</string>
<key>i4j.allowPassthrough</key>
<true/>
<key>i4j.minVersion</key>
<string>1.8</string>
<key>i4j.maxVersion</key>
<string></string>
<key>i4j.allowBeta</key>
<true/>
<key>i4j.vmIdPrefix</key>
<string></string>
<key>JavaVM</key>
<dict>
<key>MainClass</key>
<string>com.install4j.runtime.launcher.MacLauncher</string>
<key>VMOptionArray</key>
<array>
<string>-Dfile.encoding=UTF-8</string>
<string>-Dazureus.nativelauncher=1</string>
<string>-Xmx256m</string>
<string>-XstartOnFirstThread</string>
<string>-Dazureus.app.name=Vuze</string>
<string>-Dazureus.install.path=/Users/Shared/Library/Application Support/Vuze</string>
<string>-Dinstall4j.launcherId=39101</string>
<string>-Dinstall4j.swt=true</string>
<string>-Djava.library.path=/Users/Shared/Library/Application Support/Vuze/dll</string>
<string>-Dexe4j.moduleName=$APP_PACKAGE</string>
</array>
<key>OptionsFile</key>
<string>$APP_PACKAGE/Contents/vmoptions.txt</string>
<key>ArgumentArray</key>
<array>
</array>
<key>SearchSequence</key>
<array>
<string>Y</string>
<string>EJAVA_HOME</string>
<string>EJDK_HOME</string>
</array>
<key>VersionInfo</key>
<string>0_198139810</string>
<key>ClassPath</key>
<string>$APP_PACKAGE/../.install4j/i4jruntime.jar:/Users/Shared/Library/Application Support/Vuze/swt.jar:/Users/Shared/Library/Application Support/Vuze/Azureus2.jar</string><!-- I4J_INSERT_CLASSPATH -->
<key>WorkingDirectory</key>
<string>$APP_PACKAGE/../../../../../../../../Users/Shared/Library/Application Support/Vuze</string>

[parg]

Exactly - change that to

<string>-Xmx512m</string>

and see how things go! (maybe back the file up somewhere before changing it so you can copy it back if there's a problem)

[Jay]

I'm getting the exact same problem with El Capitan.

Am I going to have to start mucking about with code? I tried to install Vuze again (without uninstalling the old version) as I thought it might have been an older version or something and it still crashed/froze.

I usually only have a handful of files downloading or seeding at any one time, maybe 20 maximum.

[1914]

Thanks Parg !
You're a genius !  (:
This solved it for me .
Vuze has been running all day yesterday and all night without shutting off.
Too easy. Really appreciate your help. 
This was a recurring problem every now and then , had no idea what it was. 
............................
To the other commenter : Jay :
It's not hard. You are not "mucking around with code". 
You are changing a number in a text file, which Parg has specified, in his simple instructions.

Vuze icon --> Open Package --> Contents --> info.Plist  (open in text edit) --> (Edit the number from 256 to 512 on the line specified )

Copy the text file first just in case you find a way to muck it up. 

It's not hard. One of the easiest things in the world.
If you can type a forum post, you can change a number in a text file, I am sure of it.

[Flinxxx]

How do I do this in Windows? I tried using the command line option -Xmx512m but it says the "Current Heap maximum is 246 MB" when I look in Tools > Options > Startup & Shutdown

[1914]

Instructions in the link Parg posted earlier in the thread
http://wiki.vuze.com/w/Java_VM_memory_usage

Under the section
"Changing Memory Options"

It's slightly easier to do on Windows, apparently.

[Flinxxx]

[Image: 14in03t.jpg]

If I enter say 192MB the heap will be 192MB but when I enter anything greater than 246MB the heap will only be 246MB.

[parg]

I think that is reporting the current max usage, not the limit.

[Flinxxx]

It is always 246MB since I entered a value greater than that, and I get the following error every time I start Vuze
[Image: 4ktnh2.jpg]

[parg]

Hmm, OK, I stand corrected!

Can you go to where Vuze is installed (C:\Program Files\Vuze or C:\Program Files (x86)\Vuze most likely) and open the file

Azureus.exe.vmoptions  (use notepad or similar)

Check it has the line

-include-options ${APPDATA}\Azureus\java.vmoptions  

in it.

I assume that you are launching Vuze by calling the Azureus.exe in that same folder?