Blender crashing when geometry nodes with a large animated image sequences are used #94738

New Issue

Paul Häger · 2022-01-08T14:17:00+01:00

Paul Häger commented

2022-01-08 14:17:00 +01:00

System Information
Operating system: Linux-5.15.12-artix1-1-x86_64-with-glibc2.33 64 Bits
Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.46

32GB Ram

Blender Version
Broken: version: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-16 23:26, hash: 34d424fd64

Short description of error
When using a large animated image sequence (2100 images for example) blender crashes for me somewhere after frame 2000 while playing.
Shorter sequences (<2000) dont seem to cause any crash.

Tested both on RC and stable builds. Seems to be also happening on windows builds.

Exact steps for others to reproduce the error

I have not yet found a way to consistently reproduce this. Sometimes it manages to go through all 6519 Frames, and sometimes
it crashes. The frame count has been > 3000 at the time of the crashes at least. Once crash occured when image was rendered during playback

music test.crash.txt
#94738.crash.txt
music test.blend

I removed any frames after 2100 from this file but the original sequence had ~6800 Frames, so if you need a larger sequence for testing I can provide that too.

**System Information** Operating system: Linux-5.15.12-artix1-1-x86_64-with-glibc2.33 64 Bits Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.46 32GB Ram **Blender Version** Broken: version: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-16 23:26, hash: `34d424fd64` **Short description of error** When using a large animated image sequence (2100 images for example) blender crashes for me somewhere after frame 2000 while playing. Shorter sequences (<2000) dont seem to cause any crash. Tested both on RC and stable builds. Seems to be also happening on windows builds. **Exact steps for others to reproduce the error** I have not yet found a way to consistently reproduce this. Sometimes it manages to go through all 6519 Frames, and sometimes it crashes. The frame count has been > 3000 at the time of the crashes at least. Once crash occured when image was rendered during playback [music test.crash.txt](https://archive.blender.org/developer/F12799170/music_test.crash.txt) [#94738.crash.txt](https://archive.blender.org/developer/F12811861/T94738.crash.txt) [music test.blend](https://archive.blender.org/developer/F12795968/music_test.blend) I removed any frames after 2100 from this file but the original sequence had ~6800 Frames, so if you need a larger sequence for testing I can provide that too.

Paul Häger commented

2022-01-08 14:17:00 +01:00

Added subscriber: @PaulHaeger

Germano Cavalcante commented

2022-01-10 04:17:27 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2022-01-10 04:17:27 +01:00

Could you provide the sequence of images used?
Apparently the packing of movies and image sequences in the .blend file is not supported. So the file is missing the images.

Could you provide the sequence of images used? Apparently the packing of movies and image sequences in the .blend file is not supported. So the file is missing the images.

Jesse Yurkovich commented

2022-01-10 09:51:10 +01:00

Added subscriber: @deadpin

Jesse Yurkovich commented

2022-01-10 09:51:10 +01:00

From the crash file it looks like it's another duplicate of #92740/T94266 and the fix will go out in 3.0.1 if/when that release is decided.

Note: As of right now, none of the fixes that are being considered have been checked into the 3.0.1 build yet. In order to try out the fix, you'll have to grab a 3.1 build.

From the crash file it looks like it's another duplicate of #92740/T94266 and the fix will go out in 3.0.1 if/when that release is decided. Note: As of right now, none of the fixes that are being considered have been checked into the 3.0.1 build yet. In order to try out the fix, you'll have to grab a 3.1 build.

Paul Häger commented

2022-01-10 13:49:46 +01:00

In #94738#1285410, @mano-wii wrote:
Could you provide the sequence of images used?
Apparently the packing of movies and image sequences in the .blend file is not supported. So the file is missing the images.

Here are the images.

imgdata.tar.gz

In #94738#1285504, @deadpin wrote:
From the crash file it looks like it's another duplicate of #92740/T94266 and the fix will go out in 3.0.1 if/when that release is decided.

Note: As of right now, none of the fixes that are being considered have been checked into the 3.0.1 build yet. In order to try out the fix, you'll have to grab a 3.1 build.

I will later today test this in the 3.1 build, thanks for the info!

> In #94738#1285410, @mano-wii wrote: > Could you provide the sequence of images used? > Apparently the packing of movies and image sequences in the .blend file is not supported. So the file is missing the images. Here are the images. [imgdata.tar.gz](https://archive.blender.org/developer/F12798751/imgdata.tar.gz) > In #94738#1285504, @deadpin wrote: > From the crash file it looks like it's another duplicate of #92740/T94266 and the fix will go out in 3.0.1 if/when that release is decided. > > Note: As of right now, none of the fixes that are being considered have been checked into the 3.0.1 build yet. In order to try out the fix, you'll have to grab a 3.1 build. I will later today test this in the 3.1 build, thanks for the info!

Paul Häger commented

2022-01-10 16:39:48 +01:00

I have been testing the latest 3.1 Build. Seems a lot more stable and I can use a larger set of images.

However there have still been some sporadic crashes. I have not yet found a way to consistently reproduce this. Sometimes it manages to go through all 6519 Frames, and sometimes
it crashes. The frame count has been > 3000 at the time of the crashes at least. If this is related to this issue or not I dont know.

I attached the log of the last crash I had: music test.crash.txt

If I can find out more I will report it.

I have been testing the latest 3.1 Build. Seems a lot more stable and I can use a larger set of images. However there have still been some sporadic crashes. I have not yet found a way to consistently reproduce this. Sometimes it manages to go through all 6519 Frames, and sometimes it crashes. The frame count has been > 3000 at the time of the crashes at least. If this is related to this issue or not I dont know. I attached the log of the last crash I had: [music test.crash.txt](https://archive.blender.org/developer/F12799170/music_test.crash.txt) If I can find out more I will report it.

Richard Antalik commented

2022-01-19 21:28:46 +01:00

Added subscribers: @mont29, @Sergey, @iss

Richard Antalik commented

2022-01-19 21:28:46 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Richard Antalik commented

2022-01-19 21:28:46 +01:00

I was able to cause crash too, this happened when I hit render, but I was not able to reproduce this anymore. It is evident from my crash file, that I was fuzzing around. Also my trace is different than previous one so it's possible there are more causes. Will confirm even though this seems to be very hard to reproduce.

#94738.crash.txt

CC @Sergey, @mont29

Also note that I have reduced cache size limit to increase likelyhood of crash, but not quite sure if this did have any effect.

I was able to cause crash too, this happened when I hit render, but I was not able to reproduce this anymore. It is evident from my crash file, that I was fuzzing around. Also my trace is different than previous one so it's possible there are more causes. Will confirm even though this seems to be very hard to reproduce. [#94738.crash.txt](https://archive.blender.org/developer/F12811861/T94738.crash.txt) CC @Sergey, @mont29 Also note that I have reduced cache size limit to increase likelyhood of crash, but not quite sure if this did have any effect.

Bastien Montagne commented

2022-01-24 16:26:15 +01:00

All tracebacks end up to the same point ( movie cache code, moviecache_valfree -> MEM_CacheLimiter_unmanage), so I think this is more for the #vfx_video module than #core really?

All tracebacks end up to the same point ( movie cache code, `moviecache_valfree -> MEM_CacheLimiter_unmanage`), so I think this is more for the #vfx_video module than #core really?

Sergey Sharybin commented

2022-03-11 15:37:26 +01:00

I was unable to reproduce the issue so far, but found an issue in the related area which got addressed in f4c8b4eb3e.
Took a while for all builds to get ready. Please give it a test again!

I was unable to reproduce the issue so far, but found an issue in the related area which got addressed in f4c8b4eb3e. Took a while for all builds to get ready. Please give it a test again!

Paul Häger commented

2022-03-11 23:47:46 +01:00

Will do!

Unfortunately I'm away for a few days so I can't test it until Wednesday at the soonest.

Will do! Unfortunately I'm away for a few days so I can't test it until Wednesday at the soonest.

Paul Häger commented

2022-03-18 17:05:14 +01:00

I tested the 9097c97767 Build since it was the closest to the commit f4c8b4eb3e.

I gave it some stress testing and Blender did not crash once. The issue seems fixed now, thank you very much.

I tested the 9097c97767 Build since it was the closest to the commit f4c8b4eb3e. I gave it some stress testing and Blender did not crash once. The issue seems fixed now, thank you very much.

Paul Häger commented

2022-03-18 17:05:55 +01:00

Im going to set this issue to resolved unless anything speaks against it.

Paul Häger commented

2022-03-18 17:06:13 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Paul Häger closed this issue

2022-03-18 17:06:13 +01:00

Sergey Sharybin commented

2022-03-18 17:39:14 +01:00

Thanks for the report and testing!

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender crashing when geometry nodes with a large animated image sequences are used #94738