2.80 32-bit appears broken (on 64-bit Windows at least) #60089

New Issue

Gavin Scott · 2019-01-02T21:32:59+01:00

Gavin Scott commented

2019-01-02 21:32:59 +01:00

System Information
Windows 10 64-bit, Nvidia 1060

Blender Version
Broken: Current 32-bit 2.80 daily
blender-2.80-4dd0a90f4213-win32

Short description of error
Blender intermittently fails to start, fails to read date/hash, silently quits opening .blend, throws exception on exit, etc.

Exact steps for others to reproduce the error
After reading

https://devtalk.blender.org/t/bl-2-80-beta-will-not-run-on-win-10/4757

I downloaded the current 2.80 32-bit beta and it definitely seems to have issues, at least running on top of current Windows 64-bit (I don't have a 32-bit system to test on currently).

It will fail to start (exits silently) most (all?) of the time when started normally.
It will start when run with --debug, but throws an EXCEPTION_ACCESS_VIOLATION if you immediately quit.
Opening any .blend file has about a 50% chance of causing an immediate exit with the same exception.
The --debug output shows "Version 280 sub 39 date unknown hash unknown" about half the time, but the rest of the time it finds the date and hash successfully.

**System Information** Windows 10 64-bit, Nvidia 1060 **Blender Version** Broken: Current 32-bit 2.80 daily blender-2.80-4dd0a90f4213-win32 **Short description of error** Blender intermittently fails to start, fails to read date/hash, silently quits opening .blend, throws exception on exit, etc. **Exact steps for others to reproduce the error** After reading https://devtalk.blender.org/t/bl-2-80-beta-will-not-run-on-win-10/4757 I downloaded the current 2.80 32-bit beta and it definitely seems to have issues, at least running on top of current Windows 64-bit (I don't have a 32-bit system to test on currently). It will fail to start (exits silently) most (all?) of the time when started normally. It will start when run with --debug, but throws an EXCEPTION_ACCESS_VIOLATION if you immediately quit. Opening any .blend file has about a 50% chance of causing an immediate exit with the same exception. The --debug output shows "Version 280 sub 39 date unknown hash unknown" about half the time, but the rest of the time it finds the date and hash successfully.

Gavin Scott commented

2019-01-02 21:32:59 +01:00

Added subscriber: @GavinScott

blender-admin commented

2019-01-02 21:32:59 +01:00

#61404 was marked as duplicate of this issue

Ray molenkamp commented

2019-01-02 22:02:03 +01:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2019-01-02 22:02:03 +01:00

Can't reproduce on win64, try starting with --factory-startup and see if that helps.

Can't reproduce on win64, try starting with `--factory-startup` and see if that helps.

Gavin Scott commented

2019-01-02 22:40:22 +01:00

Running with --factory-startup makes no difference in the behavior that I can detect. Out of the box it just exits silently.

Ah, it did that four times in a row and then finally started correctly on the fifth try.

It's definitely some kind of non-deterministic uninitialized variable kind of thing.

Running with --factory-startup makes no difference in the behavior that I can detect. Out of the box it just exits silently. Ah, it did that four times in a row and then finally started correctly on the fifth try. It's definitely some kind of non-deterministic uninitialized variable kind of thing.

Sebastian Parborg commented

2019-01-24 17:29:26 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-01-24 17:29:26 +01:00

Is this still a problem with the latest blender beta?

Gavin Scott commented

2019-01-24 18:23:57 +01:00

With today's 2.80 32-bit download I still get the same behaviors. Silently exits unless you add --debug, and then it's working sort of OK, though one file fails to render objects in Cycles, and I get various errors in the process of opening random .blend files (some of which may be old 2.79 format), and it generally crashes when I exit.

Memoryblock reconstruct: end corrupt
Memoryblock reconstruct: end corrupt
Memoryblock reconstruct: end corrupt
Memoryblock reconstruct: end corrupt
Memoryblock reconstruct: end corrupt
Memoryblock reconstruct: end corrupt
Memoryblock reconstruct: end corrupt
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x3F800000

Again, this is just be trying out 32-bits on a 64-bit Windows because other people reported issues with it. I don't have a true 32-bit Windows system to test on, and have no personal need for 32 to work on 64, so my only concern was whether this represents an actual issue which would affect users on 32-bit platforms.

With today's 2.80 32-bit download I still get the same behaviors. Silently exits unless you add --debug, and then it's working sort of OK, though one file fails to render objects in Cycles, and I get various errors in the process of opening random .blend files (some of which may be old 2.79 format), and it generally crashes when I exit. Memoryblock reconstruct: end corrupt Memoryblock reconstruct: end corrupt Memoryblock reconstruct: end corrupt Memoryblock reconstruct: end corrupt Memoryblock reconstruct: end corrupt Memoryblock reconstruct: end corrupt Memoryblock reconstruct: end corrupt Error : EXCEPTION_ACCESS_VIOLATION Address : 0x3F800000 Again, this is just be trying out 32-bits on a 64-bit Windows because other people reported issues with it. I don't have a true 32-bit Windows system to test on, and have no personal need for 32 to work on 64, so my only concern was whether this represents an actual issue which would affect users on 32-bit platforms.

Sebastian Parborg commented

2019-01-24 18:30:07 +01:00

@LazyDodo can you take a look at this?

Ray molenkamp commented

2019-01-24 19:07:05 +01:00

I have, i can't reproduce

Sebastian Parborg commented

2019-01-24 20:12:39 +01:00

Added subscriber: @brecht

Sebastian Parborg commented

2019-01-24 20:12:39 +01:00

@brecht do you guys have any windows computers to reproduce this on?

Gavin Scott commented

2019-01-24 20:29:05 +01:00

If it doesn't reproduce for LazyDodo then I'm not sure it's worth worrying too much about at the moment, unless and until a real 32-bit user comes along with issues, so I have no problem if you want to close this one.

There might be some fundamental 32-bit environment issue here that I don't normally see because I don't run similar 32-bit applications. As long as it works for someone then I'm not going to worry that it's completely broken which was my original concern.

If it doesn't reproduce for LazyDodo then I'm not sure it's worth worrying too much about at the moment, unless and until a real 32-bit user comes along with issues, so I have no problem if you want to close this one. There might be some fundamental 32-bit environment issue here that I don't normally see because I don't run similar 32-bit applications. As long as it works for someone then I'm not going to worry that it's completely broken which was my original concern.

Richard Antalik commented

2019-01-24 20:50:01 +01:00

Added subscriber: @iss

Richard Antalik commented

2019-01-24 20:50:01 +01:00

seems similar to #59926
Haven't realized, this may be only present in 32bit build. i switched to 64, haven't noticed bug anynore and closed it.
I can still reproduce also #59927 on 32-bit

seems similar to #59926 Haven't realized, this may be only present in 32bit build. i switched to 64, haven't noticed bug anynore and closed it. I can still reproduce also #59927 on 32-bit

Sebastian Parborg commented

2019-01-26 13:36:28 +01:00

Does it work if you run the 32bit version in compatibility mode with win7 (32bit) ?

I've had an other user report that on win7 64bit he also got this issue, but after running it in compatibility mode, this doesn't happen (even when switching it off afterwards).

Seems like people had problems like this with java too https://stackoverflow.com/questions/8921607/jvm-32-bit-crashes-on-64-bit-machine

Does it work if you run the 32bit version in compatibility mode with win7 (32bit) ? I've had an other user report that on win7 64bit he also got this issue, but after running it in compatibility mode, this doesn't happen (even when switching it off afterwards). Seems like people had problems like this with java too https://stackoverflow.com/questions/8921607/jvm-32-bit-crashes-on-64-bit-machine

Ovionis commented

2019-01-27 00:22:03 +01:00

Added subscriber: @Phigon

Gavin Scott commented

2019-01-27 15:20:58 +01:00

Quick tests don't show any apparent difference with Windows 7 compatibility mode.

Ovionis commented

2019-01-27 15:40:11 +01:00

I never bothered setting to Win7 compatibility.
The default target in Win7 is WinXp SP3.
For my Win10 (laptop) test, I used the default Win8 target.

The compatibility switch on/off thing didn't stick on Win10.

I never bothered setting to Win7 compatibility. The default target in Win7 is WinXp SP3. For my Win10 (laptop) test, I used the default Win8 target. The compatibility switch on/off thing didn't stick on Win10.

Brecht Van Lommel commented

2019-02-11 13:57:31 +01:00

Added subscribers: @benjamin63, @JacquesLucke

ben benjamin commented

2019-02-11 14:47:42 +01:00

as for me the "compatibility with windows 7" trick works

ChristopherAnderssarian commented

2019-03-11 15:24:12 +01:00

Added subscriber: @ChristopherAnderssarian

Philip Holzmann commented

2019-04-02 15:47:49 +02:00

Added subscriber: @Foaly

Philip Holzmann commented

2019-04-02 15:47:49 +02:00

The 32 bit build also crashes sometimes on startup for me, but not consistently.
Sometimes I also get

 Memoryblock reconstruct: end corrupt

in the log.
Would it help if I did a 32 bit debug build myself to see where it crashes?

The 32 bit build also crashes sometimes on startup for me, but not consistently. Sometimes I also get ``` Memoryblock reconstruct: end corrupt ``` in the log. Would it help if I did a 32 bit debug build myself to see where it crashes?

Brecht Van Lommel commented

2019-04-02 16:15:38 +02:00

Please try again with the very latest 2.80 32bit build:
https://builder.blender.org/download/

4f4cea727e may have fixed some or all of these issues.

Please try again with the very latest 2.80 32bit build: https://builder.blender.org/download/ 4f4cea727e may have fixed some or all of these issues.

ben benjamin commented

2019-04-02 16:43:21 +02:00

works great for me now, no crash anymore (so far).