I just got a crash report, but without actual crash. Still undesired behaviour....

There were pending updates, so I waited until all downloads finished.

Immediately upon the last download finishing (bubble notify), I started the update. I was unaware that at this time the extract (rar archive) of the last finished download was running.

The update finished and restarted jd2 without giving any warning or error. (I assume the extract was still running and interrupted by that.

When jd2 started again it reported:

JDownloader crashed

It seems that there was a crash while extracting an archive.
Check the details below. Do you want to send a bug report?

This error was caused by:

1467845090478 - Archive Name: Mxxxxx
1467845090478 - Archive Path: D:\download\Mxxxxx.part1.rar
1467845090480 - Date: Wed Jul 06 23:44:50 BST 2016
1467845090480 - Start Extracting
1467845090481 - Extension Setup:
{
"blacklistpatterns" : [ "##Lines with XX are comments", "##.*\\.jpe?g"],
"deepextractionenabled" : true,
"deletearchivefilesafterextractionaction" : "RECYCLE",
"deleteinfofilesafterextraction" : false,
"maxcheckedfilesizeduringoptimizedpasswordfindinginbytes" : 1024000,
"iffileexistsaction" : "AUTO_RENAME",
"customextractionpathenabled" : false,
"askforunknownpasswordsenabled" : true,
"subpath" : "%PACKAGENAME%",
"bubblecontentarchivenamevisible" : true,
"latestiffileexistsaction" : "OVERWRITE_FILE",
"deletearchivedownloadlinksafterextraction" : false,
"bubblecontentextracttofoldervisible" : true,
"lastworkinglibid" : "Windows-x86",
"subpathenabled" : false,
"enabled" : true,
"useoriginalfiledate" : false,
"freshinstall" : false,
"guienabled" : false,
"writeextractionlogenabled" : true,
"bubblecontentcircleprogressvisible" : true,
"passwordfindoptimizationenabled" : true,
"bubbleenabledifarchiveextractionisinprogress" : true,
"subpathminfolderstreshhold" : 0,
"restorefilepermissions" : true,
"bubblecontentstatusvisible" : true,
"customextractionpath" : "D:\\download",
"cpupriority" : "HIGH",
"subpathminfilesorfolderstreshhold" : 2,
"passwordlist" : [ "12345" ],
"bubblecontentdurationvisible" : true,
"subpathminfilestreshhold" : 0,
"askforpassworddialogtimeoutinms" : 600000,
"oldpwlistimported" : true,
"deepextractionblacklistpatterns" : [ "##Lines with XX are comments", "##Skip deep extraction of archives that contain exe files", ".*\\.exe" ],
"bubblecontentcurrentfilevisible" : true
}
1467845090481 - Archive Setup:
{
"autoExtract" : "UNSET",
"extractionInfo" : null,
"extractPath" : null,
"finalPassword" : null,
"ifFileExistsAction" : null,
"passwords" : [ ],
"removeDownloadLinksAfterExtraction" : "UNSET",
"removeFilesAfterExtraction" : "UNSET"
}
1467845090481 - (DownloadLinkArchiveFile)File: D:\download\Mxxxxx.part1.rar
1467845090481 - (DownloadLinkArchiveFile)File: D:\download\Mxxxxx.part2.rar
1467845090481 - Prepare
1467845090588 - Extract To: D:\download
1467845090589 - Use Password: null|PW Protected:false:false
1467845090589 - Start Extracting org.jdownloader.extensions.extraction.multi.Multi@d5be47

This should not be reported as crash. jd should ask before exiting what to do.

[Jiaz]

Do you have a hs_err file in your JDownloader folder?
I think the bug is that JDownloader thought it crashed because of the unfinished extraction job. I will review this code and fix it to not report this

I looked (also in subfolders), but did not see any hs_err file.

I was asked if it should upload the crash data and I had declined.
Also I had a few restarts since, so I dont know if that file would have been kept.

But yes, I had an half extracted file (only part of the size it should have), and the rar files were still present (they go to recycle bin, if extract fininshed)

[Jiaz]

Fixed the underlying cause of the *false crash report* JDownloader restarted during extraction and that made JDownloader think it crashed during extraction.

[Statter]

hmmm been on vacation came back and got an extraction error on updating JDownloader .....

Hopefully this is what you mentioned and it is now fixed for future updates ..
I closed and restarted JD and it seems fine atm but just incase you all want to look at the error report it is or should be I believe in.
Error Extracting update
27.08.16 20.53.59 <--> 27.08.16 20.54.52 jdlog://1234281887641/

Sorry for posting here but it seemed to be the latest report on such.

Thanks again for all the great work you all do.

[Jiaz]

Thanks for the feedback! Just report back when it happens again!