#1
|
|||
|
|||
JDownloader2.exe + JDownloaderSetup.exe
JDownloader2.exe + JDownloaderSetup.exe *32
Why are two processes in Task Manager? Setup? - I did not install (!)
Spoiler:
updateError.txt http://jdownloader.org/pastebin/122446 http://jdownloader.org/pastebin/122448 10.03.2014 error.txt Not working Update (no reaction) http://jdownloader.org/pastebin/122445 10.03.14 13.51.02to10.03.14 13.54.52 jdlog://2380934130931/ EDIT: and NEXT PROBLEM: After the restart JD2 appeared the same two processes: JDownloader2.exe (Launcher) JDownloader2.exe (Launcher) (high CPU) Double Process (Double run JD2) ==== EDIT: Last edited by djmakinera; 10.03.2014 at 18:30. |
#2
|
||||
|
||||
JDownloaderSetup.exe is app started from WebInstaller or offline installer. Normal JD2 update doesn't use exe files.
It looks like you started 32 bit install. |
#3
|
|||
|
|||
editestowy - a co najdziwniejsze - jak to możliwe, że miałem taki przypadek, że jeden program uruchomił się w dwóch procesach (2 programy)
Teoretycznie to nie możliwe bo program ma "lock" - więc niemożliwością by było uruchomienia kilku okien... a jednak miałem taki przypadek... Instalacja 32-bit ...to było ze 2 lata temu... Teraz tylko instaluje ZAWSZE 64-bit ... |
#4
|
||||
|
||||
There is no JdownloaderSetup.exe file in the JD2 installation folder, so it looks like you started it by yourself.
JdownloaderSetup.exe may be from web installer, but for 64 bit OS it should be 64 bit app NOT 32 bit (official webinstaller uses 32 bit setup on 32 bit OS, 64 bit setup on 64 bit OS): You have big mess with your installations, maybe some from JD1, some from very old JD2 (as I see from screenshots you PM me - old offline installation with Updater.jar) - so if you are experimenting, you've got "experimental" results... |
#5
|
|||
|
|||
editestowy - dlaczego więc po instalacji są błędy w logach?
|
#6
|
||||
|
||||
Only error I've got in error.log is:
"java.lang.ClassCastException: java.util.logging.LogManager cannot be cast to org.jdownloader.logging.ExtLogManager" - so probably something in the log subsytem is being changed - it doesn't affect main functions of JD. Devs probably decided that everything is logged during the launch procedure - this is why error.log is created. Create your own starter (e.g. java -jar jdownloader.jar) if the error.log disturbs you |
#7
|
|||
|
|||
Quote:
Potwierdzam - to już taką samą sytuację (jeśli dobrze zrozumiałem) javaw.exe (niski CPU) javaw.exe (wysoki CPU) Dwa procesy w MENEDŻER ZADAŃ (1 Program) Last edited by djmakinera; 14.03.2014 at 14:33. |
#8
|
||||
|
||||
In the normal work (starting JD by wrapper: jdownloader2.exe) the process should be:
jdownloader2.exe not javaw.exe Javaw process is present when you start JD by command line: java -jar jdownloader.jar Open Task Manager and check properties for the processes - are they pointing to the same file? 2 javaw.exe processes may be because of running 2 instances? |
#9
|
||||
|
||||
javaw.exe (ONE) will always run when JD runs.
The .exe is only the "starter". GreeZ psp
__________________
JD Supporter, Plugin Dev. & Community Manager
Erste Schritte & Tutorials || JDownloader 2 Setup Download |
#10
|
|||
|
|||
editestowy - Ten problem już nie występuje po wcześniejszych aktualizacji
Szkoda, że nie zrobiłem screen, bo było by ciekawie zobaczyć 2 okna z tą samą listą pobierań. |
#11
|
||||
|
||||
Current wrapper/launcher masks java(w) process:
- so java(w) is visible because of a) command line start or b) very old launcher c) other instance (as in my screenshot, second instance started from command line, different files/folders) |
#12
|
|||
|
|||
editestowy - ja nie mam JDownloader2.exe (zawsze usuwam)
uruchamiam zawsze z JDownloder.jar |
#13
|
||||
|
||||
So you're always deleting jdownloader2.exe, starting JD with command line and you're reporting:
"JDownloader2.exe + JDownloaderSetup.exe *32" ... Strange....;) Last edited by editestowy; 14.03.2014 at 23:12. |
#14
|
|||
|
|||
Wyntylator na pełnych obrotach za dużo mocy z procesora |
#15
|
||||
|
||||
Can't confirm high CPU usage, high memory usage, 2 processes...
Put your CFG into pastebin, give us link, write down your startup parameters then we can create ticket or setup TeamViewer session with jiaz. |
#16
|
|||
|
|||
editestowy - 1.
nie mam startowych parametrów ! Instalacja jest świeża. Uruchamiam tylko z JDownloader.jar UncaughtExceptionHandler.log ERRORS http://jdownloader.org/pastebin/122601 --ID:26TS:1394833374955-14-03-14 22:42:54 - [org.appwork.utils.swing.dialog.AbstractDialog$8(runInEDT)] -> Utils>Gui.log>Force Dummy Init --ID:26TS:1394833374970-14-03-14 22:42:54 - [jd.gui.swing.jdgui.JDGui$24(edtRun)] -> SilentMode: auto false --ID:26TS:1394833374987-14-03-14 22:42:54 - [jd.gui.swing.jdgui.JDGui$24(edtRun)] -> SilentMode: auto false --ID:26TS:1394833374988-14-03-14 22:42:54 - [org.appwork.utils.swing.dialog.AbstractDialog$11(runInEDT)] -> Utils>Gui.log>Reset Dummy Info --ID:26TS:1394833374989-14-03-14 22:42:54 - [org.appwork.utils.swing.dialog.AbstractDialog(displayDialog)] -> Utils>Gui.log>Display Dialog: dialog_Utw_rz_pakiet_z_logami --ID:26TS:1394833375000-14-03-14 22:42:55 - [org.appwork.utils.swing.EDTHelper.run(EDTHelper.java:93)] -> Utils>Gui.log>SEVERE Exception occurred java.lang.InternalError: Bieżący proces wykorzystał wszystkie dozwolone przez system dojścia do obiektów Window Manager. at sun.awt.windows.WToolkit.eventLoop(Native Method) at sun.awt.windows.WToolkit.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Last edited by djmakinera; 15.03.2014 at 01:03. |
Thread Tools | |
Display Modes | |
|
|