- ago
If I run the Strategy Evolver in WL8 B69, it takes less than 10 minutes and WL 8 crashes (without warning). If I do the exact same procedure in WL8 B53, the Evolver runs without any crashes. I've noticed that in WL8 B53, I have .Net Core version 6.0.6, which obviously prevents such crashes.

Is it known that the .Net Core version 6.0.2 causes Evolver crashes and which .Net Core version is the current suitable one for WL8 B69?

0
227
Solved
10 Replies

Closed

Bookmark

Sort
Glitch8
 ( 12.33% )
- ago
#1
Interesting, it’s not known, I haven’t experienced the crash but it would be interesting to see if the later framework really does prevent it,
0
- ago
#2
Since WL8 B69 is running on my super fast Dev notebook (Intel i9 FX 24 Cores - makes ~100 evolver generations in less than 5 minutes), I can do the upgrade. Which part of the .Net Core 6.0.6 framework does WL8 use?
0
Glitch8
 ( 12.33% )
- ago
#3
x64
0
- ago
#4
Windows Desktop Runtime or Runtime Installer or both?
0
Glitch8
 ( 12.33% )
- ago
#5
Windows Desktop or both, not really sure if Windows Desktop includes the core framework
0
- ago
#6
I did the .Net Core update, same problem.

I have recorded a video into the onedrive location below. At 1:24 the freeze starts and then it closes WL8 at 1:37 (without any warnings). You may be able to reproduce this for yourself. Evolver Range is Jan. 1th 2020 to Jan. 1th 2023. Shouldn't take longer than 10 minutes.

QUOTE:
https://1drv.ms/v/s!AgcaLpBtmcLkjLli63nVwAaqKnF_RA?e=mRwndL
0
- ago
#7
If it isn't reproducible for you then I know that it may be related with a change in my custom scorecard extension, so I'll have to get back to the versioning on Github to see when I have added or changed anything in the past weeks and revert it back.
0
Glitch8
 ( 12.33% )
- ago
#8
OK I just got back from Starbucks and my production B69 Evolver has been running for over one hour with no crash.

1
Best Answer
Cone8
 ( 27.64% )
- ago
#9
Windows Desktop Runtime is the correct installation.
Which-NET-runtime
1
- ago
#10
I have to apologize, because the crash was caused by a self-built custom strategy gene (only added in Dev environment), which is in use since mid-December 2023.
0

Closed

Bookmark

Sort