#1
|
|||
|
|||
Jd2 crashes during automatic each new update EXCEPTION_STACK_OVERFLOW
Jd2 crashes during automatic each new update EXCEPTION_STACK_OVERFLOW
when run jd2 or exit instalation Code:
Last edited by Jiaz; 07.05.2020 at 11:00. |
#2
|
||||
|
||||
That crash happens outside JDownloader in # V [jvm.dll+0x215127]
OutOfMemoryError java_heap_errors=2 -> Looks like your system went Out-of-Memory and Java died because of this. Out of our hands
__________________
JD-Dev & Server-Admin |
#3
|
|||
|
|||
I have the latest version. I recently installed:
Java 8 Update 251 (64-bit). Does this version contain a lot of errors .pid, because every few days I have errors when running JD2. Where to download older versions of Java 8 again? |
#4
|
|||
|
|||
Quote:
My startup parameter -Xmx3G Not enough? |
#5
|
||||
|
||||
It's not out Out-of-Memory of Java but of your System. Java cannot get memory to work with from your system.
__________________
JD-Dev & Server-Admin |
#6
|
|||
|
|||
How much physical memory should I have on the system?
Do I need to buy more physical memory? **External links are only visible to Support Staff****External links are only visible to Support Staff** |
#7
|
|||
|
|||
There are no new updates, so it works fine for now.
I used commandline flags Code:
-Xms1G -Xmx4G -XX:-UseParallelGC -XX:-UseGCOverheadLimit -XX:+HeapDumpOnOutOfMemoryError -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:gc.log -jar Code:
Java HotSpot(TM) 64-Bit Server VM (25.251-b08) for windows-amd64 JRE (1.8.0_251-b08), built on Mar 12 2020 06:31:49 by "" with MS VC++ 10.0 (VS2010) Memory: 4k page, physical 20908164k(14325004k free), swap 21954840k(12622192k free) CommandLine flags: -XX:+HeapDumpOnOutOfMemoryError -XX:InitialHeapSize=1073741824 -XX:MaxHeapSize=4294967296 -XX:+PrintGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:-UseGCOverheadLimit -XX:-UseLargePagesIndividualAllocation -XX:+UseParallelGC 1.023: [GC (Metadata GC Threshold) [PSYoungGen: 126317K->15343K(305664K)] 126317K->15367K(1005056K), 0.0215708 secs] [Times: user=0.05 sys=0.00, real=0.02 secs] 1.045: [Full GC (Metadata GC Threshold) [PSYoungGen: 15343K->0K(305664K)] [ParOldGen: 24K->14761K(699392K)] 15367K->14761K(1005056K), [Metaspace: 20745K->20745K(1069056K)], 0.0344759 secs] [Times: user=0.06 sys=0.00, real=0.03 secs] 1.723: [GC (Metadata GC Threshold) [PSYoungGen: 63186K->7125K(361472K)] 77947K->21958K(1060864K), 0.0103776 secs] [Times: user=0.05 sys=0.00, real=0.01 secs] 1.733: [Full GC (Metadata GC Threshold) [PSYoungGen: 7125K->0K(361472K)] [ParOldGen: 14833K->13753K(739328K)] 21958K->13753K(1100800K), [Metaspace: 34494K->34489K(1079296K)], 0.0371504 secs] [Times: user=0.09 sys=0.00, real=0.04 secs] 2.588: [GC (System.gc()) [PSYoungGen: 116005K->21398K(478208K)] 129758K->35159K(1217536K), 0.0107907 secs] [Times: user=0.03 sys=0.00, real=0.01 secs] 2.599: [Full GC (System.gc()) [PSYoungGen: 21398K->0K(478208K)] [ParOldGen: 13761K->30323K(739328K)] 35159K->30323K(1217536K), [Metaspace: 44576K->44576K(1089536K)], 0.0953851 secs] [Times: user=0.31 sys=0.00, real=0.10 secs] 4.349: [GC (Allocation Failure) [PSYoungGen: 456704K->43492K(524800K)] 487027K->114810K(1264128K), 0.0459344 secs] [Times: user=0.11 sys=0.05, real=0.05 secs] 5.429: [GC (Allocation Failure) [PSYoungGen: 524772K->43490K(524800K)] 596090K->235155K(1264128K), 0.0868289 secs] [Times: user=0.26 sys=0.06, real=0.09 secs] 6.883: [GC (Allocation Failure) [PSYoungGen: 524770K->43511K(585216K)] 716435K->344644K(1324544K), 0.0913523 secs] [Times: user=0.31 sys=0.06, real=0.09 secs] 8.722: [GC (Allocation Failure) [PSYoungGen: 585207K->149600K(738816K)] 886340K->450741K(1478144K), 0.0920329 secs] [Times: user=0.33 sys=0.00, real=0.09 secs] 9.055: [GC (System.gc()) [PSYoungGen: 231704K->163369K(1012736K)] 532845K->464511K(1752064K), 0.0913219 secs] [Times: user=0.30 sys=0.06, real=0.09 secs] 9.146: [Full GC (System.gc()) [PSYoungGen: 163369K->0K(1012736K)] [ParOldGen: 301141K->444723K(739328K)] 464511K->444723K(1752064K), [Metaspace: 58372K->58173K(1101824K)], 0.7884172 secs] [Times: user=2.57 sys=0.02, real=0.79 secs] 10.244: [GC (GCLocker Initiated GC) [PSYoungGen: 128672K->17117K(1031680K)] 573395K->461849K(1771008K), 0.0205585 secs] [Times: user=0.06 sys=0.00, real=0.02 secs] |
#8
|
||||
|
||||
How much links do you have in list?
__________________
JD-Dev & Server-Admin |
#9
|
|||
|
|||
**External links are only visible to Support Staff****External links are only visible to Support Staff**
|
#10
|
||||
|
||||
And how much links in DownloadList?
But yes, that many links, Xmx4g is a good value
__________________
JD-Dev & Server-Admin |
#11
|
|||
|
|||
JD2 causes an unexpected memory leak while JD2 is idle. It happens at different times.
Using more than 16 GB of physical memory in the task manager and information, "close JAVA to prevent information loss". I don't know what causes such a large memory leak. New log: Java HotSpot(TM) 64-Bit Server VM (25.251-b08) for windows-amd64 JRE (1.8.0_251-b08), built on Mar 12 2020 06:31:49 by "" with MS VC++ 10.0 (VS2010) Memory: 4k page, physical 20908164k(6056724k free), swap 21954840k(3810444k free) CommandLine flags: -XX:+HeapDumpOnOutOfMemoryError -XX:InitialHeapSize=1073741824 -XX:MaxHeapSize=4294967296 -XX:+PrintGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:-UseGCOverheadLimit -XX:-UseLargePagesIndividualAllocation -XX:+UseParallelGC 2.148: [GC (Metadata GC Threshold) [PSYoungGen: 131559K->15237K(305664K)] 131559K->15261K(1005056K), 0.0123928 secs] [Times: user=0.02 sys=0.00, real=0.01 secs] 2.160: [Full GC (Metadata GC Threshold) [PSYoungGen: 15237K->0K(305664K)] [ParOldGen: 24K->14660K(699392K)] 15261K->14660K(1005056K), [Metaspace: 20796K->20796K(1069056K)], 0.0274773 secs] [Times: user=0.03 sys=0.05, real=0.03 secs] 3.043: [GC (Metadata GC Threshold) [PSYoungGen: 47116K->7074K(305664K)] 61777K->21807K(1005056K), 0.0074941 secs] [Times: user=0.03 sys=0.02, real=0.01 secs] 3.050: [Full GC (Metadata GC Threshold) [PSYoungGen: 7074K->0K(305664K)] [ParOldGen: 14732K->13672K(795648K)] 21807K->13672K(1101312K), [Metaspace: 34415K->34410K(1081344K)], 0.0273011 secs] [Times: user=0.09 sys=0.00, real=0.03 secs] 4.032: [GC (System.gc()) [PSYoungGen: 84912K->19728K(305664K)] 98584K->33408K(1101312K), 0.0116135 secs] [Times: user=0.05 sys=0.00, real=0.01 secs] 4.044: [Full GC (System.gc()) [PSYoungGen: 19728K->0K(305664K)] [ParOldGen: 13680K->28639K(795648K)] 33408K->28639K(1101312K), [Metaspace: 43077K->43077K(1087488K)], 0.0834232 secs] [Times: user=0.19 sys=0.00, real=0.08 secs] 5.442: [GC (Allocation Failure) [PSYoungGen: 262144K->43509K(369152K)] 290783K->83538K(1164800K), 0.0296945 secs] [Times: user=0.11 sys=0.02, real=0.03 secs] 6.303: [GC (Allocation Failure) [PSYoungGen: 369141K->43494K(369152K)] 409170K->161560K(1164800K), 0.0642600 secs] [Times: user=0.23 sys=0.02, real=0.06 secs] 7.114: [GC (Allocation Failure) [PSYoungGen: 369126K->43517K(439808K)] 487192K->248260K(1235456K), 0.0742836 secs] [Times: user=0.28 sys=0.03, real=0.08 secs] 8.636: [GC (Allocation Failure) [PSYoungGen: 439805K->133125K(548352K)] 644548K->337876K(1344000K), 0.0762049 secs] [Times: user=0.23 sys=0.03, real=0.08 secs] 9.982: [GC (Allocation Failure) [PSYoungGen: 529413K->177141K(793600K)] 734164K->408371K(1589248K), 0.1364347 secs] [Times: user=0.44 sys=0.06, real=0.14 secs] 12.799: [GC (Allocation Failure) [PSYoungGen: 793589K->223222K(839680K)] 1024819K->517439K(1635328K), 0.1637013 secs] [Times: user=0.47 sys=0.09, real=0.16 secs] 14.898: [GC (System.gc()) [PSYoungGen: 427743K->141968K(1113600K)] 721961K->532018K(1909248K), 0.1684442 secs] [Times: user=0.55 sys=0.11, real=0.17 secs] 15.066: [Full GC (System.gc()) [PSYoungGen: 141968K->0K(1113600K)] [ParOldGen: 390049K->510385K(795648K)] 532018K->510385K(1909248K), [Metaspace: 63727K->63637K(1105920K)], 1.0797617 secs] [Times: user=3.31 sys=0.03, real=1.08 secs] 17.483: [GC (Allocation Failure) [PSYoungGen: 824320K->25761K(850432K)] 1334705K->536154K(1646080K), 0.0375956 secs] [Times: user=0.13 sys=0.00, real=0.04 secs] 26.881: [GC (Allocation Failure) [PSYoungGen: 850081K->31005K(1111040K)] 1360474K->559021K(1906688K), 0.0482164 secs] [Times: user=0.14 sys=0.00, real=0.05 secs] 911.965: [GC (Allocation Failure) [PSYoungGen: 860957K->21071K(1105408K)] 1388973K->560031K(1901056K), 0.1094755 secs] [Times: user=0.16 sys=0.19, real=0.11 secs] 3373.232: [GC (Allocation Failure) [PSYoungGen: 851023K->28652K(1114112K)] 1389983K->576988K(1909760K), 0.0428274 secs] [Times: user=0.12 sys=0.06, real=0.04 secs] Heap PSYoungGen total 1114112K, used 561284K [0x000000076ab00000, 0x00000007bea80000, 0x00000007c0000000) eden space 849408K, 62% used [0x000000076ab00000,0x000000078b326280,0x000000079e880000) from space 264704K, 10% used [0x00000007ae800000,0x00000007b03fb0c8,0x00000007bea80000) to space 261632K, 0% used [0x000000079e880000,0x000000079e880000,0x00000007ae800000) ParOldGen total 795648K, used 548335K [0x00000006c0000000, 0x00000006f0900000, 0x000000076ab00000) object space 795648K, 68% used [0x00000006c0000000,0x00000006e177bfa0,0x00000006f0900000) Metaspace used 67283K, capacity 71941K, committed 72112K, reserved 1110016K class space used 9602K, capacity 11652K, committed 11696K, reserved 1048576K |
#12
|
|||
|
|||
Physical Memory is not released if a large linkcollector
Physical memory is not released if a large linkcollector 108 MB size.
During download, the kernel memory increases and is not released. She's growing - I'm watching it! (RAMMap or Process Explorer - High UseCalled "Page-File") Which contributes that even if I close JD2 it still shows a lot of physical memory usage! Even if I have even 20 or 32 GB of REAL physical memory - it won't change anything. All the time problems with free memory. Why is the memory not being released? How to solve the Kernel Memory problem in Java? I uninstalled Java, reinstalled it, but still the same problem. Of course I have large lists, but the memory should be freed when JD2 is closing! (So it is no longer in use). Do you understand this? |
#13
|
|||
|
|||
Here is an identical problem "Leaked RAM". linkcollector 100 MB size (100k links)
Please read: **External links are only visible to Support Staff****External links are only visible to Support Staff** Windows 7 3 Physical Memory DDR3 8GB + 8GB + 4GB RAM |
#14
|
||||
|
||||
More and more I think this is just another djmakinera account....
Same problems, same repeating questions.... There is neither a memory issue, nor a memory leak in JDownloader. Quote:
You are already trying to use 32GB of memory while your system only has 20GB RAM.
__________________
JD-Dev & Server-Admin |
#15
|
|||
|
|||
I am not the same user.
You don't have a large CFG folder (130 MB + 4 keep old), so you don't have leaks. What is the limit of links and archive size for my memory? 10000 links - maximum? Please note that I have changed some advanced settings etc. High I/O usage unfortunately increases memory usage and I can't help it. To free up memory, I have to restart the System each time to release physical memory reserved for Kernel Memory. How do I send you my advanced settings file? |
#16
|
||||
|
||||
That sounds like a memleak in Firewall/AV/Driver, anything that works in kernel but has nothing to do with JDownloader
__________________
JD-Dev & Server-Admin |
#17
|
||||
|
||||
The *keep old* doesn't have to do anything with this because those are stored on disk and not in memory. And 130MB is large, but nevertheless the java crashlog shows that you are overusing your system.
__________________
JD-Dev & Server-Admin |
#18
|
||||
|
||||
I can offer help via Teamviewer if you want but to me this is clearly no JDownloader issue
__________________
JD-Dev & Server-Admin |
#19
|
|||
|
|||
Something must suddenly cause a memory leak, but the question is what?
No known program like "Process Explorer" and 3 party will show what uses so much RAM, so how do I know what garbage is in memory? I am not an expert in this field ... I closed all programs in the taskbar, in the tray, turned off all AV / Firewall settings, but still uses 10GB RAM. But this only happens once a day. I only know that I use the only browser, and sometimes JD2 and nothing more that could use full RAM. I don't play any games, I don't use something that requires a lot of RAM. I still sometimes use the "Sleep" function (Windows 7) - Saving energy. |
#20
|
|||
|
|||
This may be caused by the "Sleep" function (Shut down button)
If at least once later, even during JD2, it still uses additional computer resources that are constantly growing. If I want to use JD2 it must be a clean JD2 start every time. But "Sleep" is needed for energy saving when the computer is inactive. |
#21
|
|||
|
|||
My Task List:
Memory consumption during upgrade **External links are only visible to Support Staff****External links are only visible to Support Staff** |
#22
|
||||
|
||||
@sharkboy: Xmx parameter defines how much memory Java is allowed to use. If you specify 4GB, then java is allowed to use up to 4GB.
__________________
JD-Dev & Server-Admin |
#23
|
|||
|
|||
Java crash - CMci Paged Memory Leak
JD2 crashes during startup. There is a big leak all the time in:
CMci Paged I found a complete list of processes, but this process is not listed. There is practically no information on Google: "CMci Paged" https://postimg.cc/rzpcX9yv |
#24
|
|||
|
|||
When running jd2 (Java Virtual Machine) are stored in kernel memory, the pools are inherently available in all. Data can never be flushed to the hard drive and is always kept in physical memory.
Of course, this seems to cause a huge increase in speed, but it causes other applications not to have enough memory to run. If you have an SSD, you do not need this default option in Windows 7, because the speed is still high. I found solution... I found tools that will disable this default option in my Windows 7 system: [Disable] Always Keep Windows Kernel In Memory |
#25
|
|||
|
|||
I finally solved too much memory usage for Java and others.
I detected poolmon.exe in the memory leak detection tool Now Kernel paging memory is not increasing, it's low, now I can fully enjoy JD2 It turned out to be the "Wise Hide Folder Pro: tool. I uninstalled the tool completely because the system driver conflicted with Java. **External links are only visible to Support Staff****External links are only visible to Support Staff** **External links are only visible to Support Staff****External links are only visible to Support Staff** **External links are only visible to Support Staff****External links are only visible to Support Staff** |
Thread Tools | |
Display Modes | |
|
|