Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Unresponsible lockdowns after stay in minimized state
#1
I've done some editing in Azureus.exe.vmoptions to solve this emerged issue, as follows
Quote:
-Dazureus.config.path=Z:\Azureusc\\
#-Dsun.java2d.d3d=false
#-Dsun.java2d.noddraw=true
#-Dsun.java2d.opengl=true
-Dawt.nativeDoubleBuffering=true
JAVA_DUMP_OPTS=ONANYSIGNAL(JAVADUMP[3],SYSDUMP[1]),ONINTERRUPT(NONE)
-server
-d64
-Xquickstart
-Xverify:none
–Xlp64k
Xgcpolicy:optthruput
-Xoptgc
#-Xnoclassgc
#-XX:UseSSE=3
-XX:+UseNewLongLShift
-XX:+UseXmmI2D
-XX:+UseXmmI2F
-XX:+UseXMMForArrayCopy
-XX:+UseUnalignedLoadStores
#-XX:+UseLargePages
#-XX:LargePageSizeInBytes=2m
#-XX:SurvivorRatio=16
#-XX:PermSize=128m
#-Xmn340m
-XX:+AggressiveHeap
-Xms1350m
-Xmx1350m
-XX:MaxDirectMemorySize=1350m
-XX:+UseCompressedOops
-XX:+AggressiveOpts
-XX:+UseThreadPriorities
-XX:+UseTLAB
-XX:+FastTLABRefill
-XX:+ResizeTLAB
-XX:+UseFastEmptyMethods
-XX:+UseFastAccessorMethods
-XX:+UseFastJNIAccessors
-XX:+UseBiasedLocking
#-XX:+UseConcMarkSweepGC
#-XX:+UseParNewGC
#-XX:+CMSClassUnloadingEnabled
#-XX:+CMSPermGenSweepingEnabled
-XX:+UseParallelGC
-XX:+DisableExplicitGC
#-XX:+CMSClassUnloadingEnabled
#-XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses
-XX:ParallelGCThreads=2
-XX:+UseParallelOldGC
-XX:+UseParallelOldGCCompacting
-XX:+UseParallelOldGCDensePrefix
-XX:+UseParallelDensePrefixUpdate
-XX:+UseAdaptiveSizePolicy
-XX:+UsePSAdaptiveSurvivorSizePolicy
-XX:+UseDepthFirstScavengeOrder
-XX:+DoEscapeAnalysis
 
....and as some time now process priority also in Below normal value to less intensive for system and long-term client work, as I think and if this really has effect of.

Besides I often updating swt, is causing the problem swt maybe?

Problem is, client just becomes unresponsible after staying some time in minimized state, and then very easy and quit closes with killing process in Task Manager, which very strange and indicative.

Recently like this is not even close observed. I'm yet suspect system's updates (64-bit Win 8.1).

So requesting good fixes for that, if anyone confirm or can reproduce or faced with.
 
Reply
#2
Sounds like Vuze didn't get back up after CPU-related stuck due simultaneous CPU-intensive use, say, by Vuze, online-streaming web-site watching (in Firefox on Win 8.1, with 8 GB memory onboard, Adobe Flashplayer and Firefox's plugincontainer.exe processes) & openvpn.exe process, because in addition I'm on paid VPN service.

Is there any fixes to provide elegant solutions with these situations? Paul? Anyone?
Reply
#3
Something is goin' up with this problem, now its just not possible bittorrenting, after some short time of startup running client become completely unresponsible due to CPU stuck. 
Reply
#4
Check the thread_1.log and thread_2.log files to find out which thread is responsible... OR send me a debug.zip file (Help menu, last option) - paul@vuze.com
Reply
#5
Yes, thanks for reply with helping, debug sending is done, now I'm testing with VPN-off, looks like things began better.
Reply
#6
I don't see anything obvious in the logs - in particular it doesn't appear that the Java runtime is using the CPU, thread usage is pretty low - perhaps it is your VPN software?

 
Reply
#7
Software are Viscosity working as I said through openvpn.exe, i.e. whole network goes-routed via this single process, which itself high on CPU load (due to VPN-connection encryptions) + with other CPU-related combinations - Vuze & watching online-streaming.

Subject of the problem seems directly in that.
Reply
#8
One more thing in this theme, now client just won't expand after staying some time in minimized state, Paul? Its client related problem or Windows?

System - Win 8.1 Ent 64-bit, Vuze - latest beta, swt - 64-bit 4.6M2 (was tried various versions), Java - 64-bit Oracle 8 Upd. 60.

Azureus.exe.vmoptions file contents...

Code:
-Dazureus.config.path=D:\Azureusc\\
#-Dsun.java2d.d3d=false
#-Dsun.java2d.noddraw=true
#-Dsun.java2d.opengl=true
#-Dawt.nativeDoubleBuffering=true
-server
-d64
#-XX:+UseLargePages
#-XX:LargePageSizeInBytes=0m
-Xms800m
-Xmx800m
#-XX:MaxDirectMemorySize=1g
-XX:+UnlockExperimentalVMOptions
-XX:+UseG1GC
-XX:ConcGCThreads=5
-XX:InitiatingHeapOccupancyPercent=70
-XX:MaxGCPauseMillis=200
-XX:ParallelGCThreads=20
#-XX:+UnlockDiagnosticVMOptions
-XX:+G1SummarizeConcMark
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  can't view old downloads after being locked out marcusj84 1 387 02-15-2017, 01:19 AM
Last Post: rossdennis92@yahoo.com
  Problem after changing motherboard LuvVuze 1 613 04-20-2016, 12:10 PM
Last Post: LuvVuze



Users browsing this thread: 1 Guest(s)