Worker Thread Terminated Unexpectedly.

[Steve Gill]

I'm getting this error when trying to compile a script that has always worked in the past:

"lzma: Worker thread terminated unexpectedly."

I've tried this several times using the command line compiler.  Sometimes it works and other times it doesn't.

= Steve

[Jernej Simončič]

What are your compression settings, and how much RAM do you have? Also, if you have an antivirus, try temporarily disabling it.

 

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

The one day you'd sell your soul for something, souls are a glut on the market.
       -- Faust's First Law of Synergism

[sa...@cybercom-software.com]

Hi Jernej,

I'm using lzma2/max, and I have 32GB RAM.  I'll try disabling Webroot but I don't think it will make any difference.

= Steve

[Jordan Russell]

That message has existed in the code for at least 15 years, and I think
this is the first time anyone has reported seeing it. Likely, the thread
crashed with an exception, but unfortunately it currently doesn't log
the exception message.

The LZMA SDK was upgraded in 6.4.0, and there were updates to the code
on the IS side that interfaces with the SDK. Perhaps a new bug was
introduced somewhere.

Which version of IS are you running? If >=6.4.0, did the error only
start after upgrading to 6.4?

You mentioned that you were using "lzma2/max". Is Compression=lzma2/max
the *only* compression-related setting you are using? i.e. no LZMA*
settings?

You mention that it works "sometimes". Does the error seem to appear
randomly? If you do 10 builds in a row, do some succeed and some fail,
and when it does fail, does it fail in a different place each time? It's
too early to say for sure, but if it is totally random, then that
*could* indicate a hardware problem like bad RAM. (Have other apps been
crashing mysteriously?)

Can you try setting LZMAUseSeparateProcess=yes? Does the error message
change?

6.4.3 will log the exception message (if any) which ought to help
diagnose what's causing the thread to terminate.

-JR

[sa...@cybercom-software.com]

Hi Jordan,

I'm sorry for the delay in replying. vI've been swamped with work.

<< Which version of IS are you running? If >=6.4.0, did the error only
start after upgrading to 6.4?  >>

I'm using 6.4 but it didn't happen immediately after updating to it.

<< You mentioned that you were using "lzma2/max". Is Compression=lzma2/max
the *only* compression-related setting you are using? i.e. no LZMA*
settings?  >>

Yes it's the only one.

<< You mention that it works "sometimes". Does the error seem to appear
randomly? If you do 10 builds in a row, do some succeed and some fail,
and when it does fail, does it fail in a different place each time? It's
too early to say for sure, but if it is totally random, then that
*could* indicate a hardware problem like bad RAM. (Have other apps been
crashing mysteriously?)  >>

It does happen randomly.  I think it may be memory related, ie. insufficient memory.  I found if I closed everything else done except FinalBuilder, it worked fine.  I have 32GB (which I have tested) so the other applications must be taking up too much memory.

<< Can you try setting LZMAUseSeparateProcess=yes? Does the error message
change?  >>

That seems to have fixed the issue!  I don't get the error, even with other apps running at the same time.

Thank you for your help!.

= Steve