Am 08.05.2017 um 02:13 schrieb green:
> clipka <ano### [at] anonymousorg> wrote:>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.6>>>> Happy testing!> > it immediately crashed on my win7 ultimate 64 box;> > pov-ray critical error> failed to initialize frontend: timed out waiting for worker thread startup> > unfortunately, it appears that the execution of an illegal instruction> at address 0x000000014001d6d3 has caused this unofficial> pov-ray build to crash. <write a dump?>
Does this happen even before you have the opportunity to start the GUI?
If so, then my first guess would be that it has something to do with the
CPU-specific optimized code. Exactly what hardware are you running the
binaries on?
Otherwise, if you get that far, please post the initial contents of the
message pane.
Also, have you tried the 32-bit binaries instead?
> this is a dual-boot machine (ubuntu 16), the source compiled and ran without> issue.
I presume that in this context you're talking about the Linux version?
Did you use the beta.6 source code there?

clipka <ano### [at] anonymousorg> wrote:
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.6>> Happy testing!
Some questions before I install this (on Windows)...
Is this a 'full' install like 3.7.1-beta 5?
If so, will it overwrite that previous beta? (I.e., should I temporarily rename
or move that previous beta's folder, if I want to keep it?)
Or will this new one reside safely alongside beta 5, in its own folder?
OR, is this install only the pvengine file, to replace another one somewhere?
I just want to make sure, before I do something dumb or irreversible...

Am 08.05.2017 um 13:04 schrieb Kenneth:
> Is this a 'full' install like 3.7.1-beta 5?> If so, will it overwrite that previous beta? (I.e., should I temporarily rename> or move that previous beta's folder, if I want to keep it?)> Or will this new one reside safely alongside beta 5, in its own folder?> > OR, is this install only the pvengine file, to replace another one somewhere?> > I just want to make sure, before I do something dumb or irreversible...
All the betas are full installation packages (as opposed to the "raw"
binaries of the 3.7.1-alpha series of releases); they are designed to
live happily alongside a "stable" 3.7.x installation (i.e. 3.7.0 in this
case), but no deliberate attempt is made whatsoever to let multiple
betas co-exist.
Some degree of separation between different betas may be achieved by
installing in a different folder, but a certain level of interference is
inevitable. Having two betas installed might also cause other problems
further down the road, e.g. the editor DLL installer may not be able to
identify the location of the new beta, and/or it may become difficult to
properly uninstall the older beta later. So it is generally not recommended.
If you want to keep beta.5 around, I would recommend backing up the
executables, then installing beta.6, and copying the beta.5 executables
back in under a different name. That way you'll normally run POV-Ray
3.7.1-beta.6, but will still be able to run beta.5 manually.

Am 08.05.2017 um 13:30 schrieb LucasGrijander:
> I also have the same error, the x86 and sse2 binaries also crash at different> addresses, my system is Windows XP64, Intel QX9650.
Such a difference in the crash addresses is to be expected.
Can you confirm that this is a 64-bit CPU without AVX support?
> Beta 5 run flawlessly.
Also, can one of you guys send a dump file to christoph at the domain
lipka-koeln.de? Thanks.

clipka <ano### [at] anonymousorg> wrote:
> Am 08.05.2017 um 02:13 schrieb green:> > clipka <ano### [at] anonymousorg> wrote:> >> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.6> >>> >> Happy testing!> >> > it immediately crashed on my win7 ultimate 64 box;> >> > pov-ray critical error> > failed to initialize frontend: timed out waiting for worker thread startup> >> > unfortunately, it appears that the execution of an illegal instruction> > at address 0x000000014001d6d3 has caused this unofficial> > pov-ray build to crash. <write a dump?>>> Does this happen even before you have the opportunity to start the GUI?
yes, immediately, instantly, without any discernible delay.
>> If so, then my first guess would be that it has something to do with the> CPU-specific optimized code. Exactly what hardware are you running the> binaries on?
old server mash-up. cpus are two xeon e5450 harpertown.
>> Otherwise, if you get that far, please post the initial contents of the> message pane.>> Also, have you tried the 32-bit binaries instead?
i tried the other two included binaries at your suggestion, exact same result.
>>> > this is a dual-boot machine (ubuntu 16), the source compiled and ran without> > issue.>> I presume that in this context you're talking about the Linux version?> Did you use the beta.6 source code there?
yes, of course.
i just now made a winconsole version. it ran fine, like the linux.

Am 08.05.2017 um 02:13 schrieb green:
> pov-ray critical error> failed to initialize frontend: timed out waiting for worker thread startup
FYI, the issue seems to be specific to CPUs without AVX support.
Something seems to be going wrong with the optimized noise
implementation there (or, more specifically, with the function intended
to determine the CPU type and come to the conclusion that no optimized
noise implementation is available for those CPUs).

Am 08.05.2017 um 17:38 schrieb clipka:
> Am 08.05.2017 um 02:13 schrieb green:>> pov-ray critical error>> failed to initialize frontend: timed out waiting for worker thread startup> > FYI, the issue seems to be specific to CPUs without AVX support.> Something seems to be going wrong with the optimized noise> implementation there (or, more specifically, with the function intended> to determine the CPU type and come to the conclusion that no optimized> noise implementation is available for those CPUs).
Kudos in this context to the folks at AMD who are currently trying to
figure out how I managed to goof up the optimizations-related code they
had provided us with.