So I guess this would mean SafePeer runs outside the JVM that azureus runs in? Don't know anything about how it's implemented, but could explain why the JVM memory cap is being ignored.
Will try testing with that plugin removed. If it really gobbles that much memory, it's not worthwhile anyway.
So I guess this would mean SafePeer runs outside the JVM that azureus runs in? Don't know anything about how it's implemented, but could explain why the JVM memory cap is being ignored.
Will try testing with that plugin removed. If it really gobbles that much memory, it's not worthwhile anyway.