Closed extrimexxx closed 1 month ago
same problem our CPU too old??????????? :) Intel Core 2 Duo E8400
SystemInformer+0x15d0e9:
00007ff70afcd0e9 c5f829b424c0040000 vmovaps xmmword ptr [rsp+4C0h],xmm6 ss:000000c4
e570f430=00007ff82ae921300000000000780076
Resetting default scope
EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ff70afcd0e9 (SystemInformer+0x000000000015d0e9) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0
also Canary 3.1.24244.0 - Worked
which CPU do you both use? On my older Core i5 Ivy Bridge laptop SI also crashes. Looks like AVX2 is required now.
AVX2 support was enabled in commit de6d1c9 most likely by mistake.
good find, in vcxproj you see the entry for AVX2
<EnableEnhancedInstructionSet>AdvancedVectorExtensions2</EnableEnhancedInstructionSet>
AVX2 support was enabled in commit https://github.com/winsiderss/systeminformer/commit/de6d1c9c11106632834d351f6da24c4c1bc52fe3 most likely by mistake.
Not done by mistake, this was done intentionally by @dmex.
I started to spot-check a bindiff of the two builds and - yes, this is prevalent thing all over the binary. So we need to make a decision to stop supporting these processors or have a better strategy for optimizing the paths that matter to retain support for the older processors. At this point in time I'm of the opinion that we revert the changes to ISA enhancements until we have better communication or strategy here. I'm discussing offline with @dmex.
I've reverted the ISA extension changes: https://github.com/winsiderss/systeminformer/commit/38f13791365b25f407f596ea14a47e60123d7302 - 👍
our CPU too old??????????? :) Intel Core 2 Duo E8400
15 years is probably too old.
AVX2 support was enabled in commit https://github.com/winsiderss/systeminformer/commit/de6d1c9c11106632834d351f6da24c4c1bc52fe3 most likely by mistake.
I assumed there wasn't anyone using processors from 15 years ago with 64bit Windows. The Steam hardware survey is also showing 95% support for AVX2:
AVX2 was added with Haswell (4th Intel iCore Gen) from 2013, so 11 years. I only use this old Laptop for testing and having a better taskmgr is a must have.
15 years is probably too old
New and new generations of processors do not bring such a performance increase as before, since they are stuck at the technological barrier of the element size. That is why planned obsolescence is introduced in the form of AVX2, AVX512, AVX100500, only so that people buy more and more new generations, which are actually useless. Focusing on steam is pointless, since its users are those who play performance-intensive games, and therefore buy new hardware much more often than ordinary users, who are quite satisfied with the performance of what was created in 2013. If PH requires AVX2, I will simply stay on the old version and will no longer update it, if I find an alternative, I will throw it out completely. Of course, it is unpleasant that you went the way of adobe with their f***ing AVX2.
Why should I buy a new computer? Just so that it has AVX100500? I do not play performance-intensive games.
@dmex Many modern software (his newest version) run without problems on the processor 2008 year: Win10, Far, Windows Terminal, Chrome, Firefox, VirtualBox, Aimp,7z... I think 99% modern software is work.
About this, I got the same issue when updating to that Canary build. But for now, I'll wait another build comes out soon for this.
which CPU do you both use? On my older Core i5 Ivy Bridge laptop SI also crashes. Looks like AVX2 is required now.
@MagicAndre1981 I have really old CPU here, Intel Core i3 350M, released in 2011. So yeah, that's why also I got crashed too on the latest Canary build.
Absolutely same, i'm user amd phenom ii x6 processor, that supports only maximum SSE4 instructions. I think that all these optimizations with the help of avx avx instructions are insignificant, and now the program cannot be run, and this is sad
new version 3.1.24266.0 (bf387c77) works on my old CPU again:
So issue can be closed.
Thanks!
@dmex thanks for the fix and please do not break it again in future.
as @rextheleopard wrote modern CPU's are not much faster then older once, hence there is no good reason to waste money and earths resources on replacing them.
A 3 year old zen2 32 core threadripper gets 48k points in passmark, in comparison a dual Xeon V2 2x8 cores still gets 20k points, that's 2013 technology and per core only marginally slower than the last gen threadripper. The Zeon has 2k/core and the Zen2 3k/core that's 50% on a decade. Only the latest Zen 4 threadripper gives me 4k/core hence is twice as fast per core as a 12 year old Xeon V2.
I have here a bunch of Xeon V2 systems all with DDR3 About 1,5 TB of DDR3 in total spread across half a dozen of systems, there is absolutely no point in replacing them they work great and do what they need to do with ample power to spare.
Summary: On modern CPU's ISA optimizations in SystemInformer don't mater And on old CPU's ISA optimizations in SystemInformer don't work
Brief description of your issue
dump in attachment dump.zip
Steps to reproduce (optional)
No response
Expected behavior (optional)
No response
Actual behavior (optional)
3.1.24244.0 - Worked 3.1.24258.0 - Crash on start
Environment (optional)