| Bastien Montagne (mont29) |
| Phil Stopford (philstopford) | |
| Aug 5 2018, 10:52 PM |
| Bastien Montagne (mont29) |
| Henrik Berglund (cyaoeu) |
| Phil Stopford (philstopford) |
| s12a (s12a) |
| Yevgeny Makarov (jenkm) |
System Information
Win 10 Pro x64, GTX 1060 6 GB
Blender Version
Broken: 2.79b rB9a080d2ea60
Worked: (optional)
Short description of error
Exact steps for others to reproduce the error
Fire up blender.
Create a uv sphere.
Assign a material.
Load white.png into the diffuse color slot. Engage viewport, render. Blender will be fine.
Re-do these steps using white.exr. Blender will crash shortly after loading the image.
Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
I'm not sure what the objection is. Providing a blend file is not helpful here - the crash happens loading the EXR image in. I've supplied PNG and the resulting EXR file so that the crash can be better understood (PNG is not crashing, EXR is). Steps are provided. Release information and OS/graphics card information is provided.
I don't see what I missed or did wrong here. Can you provide explicit guidance to satisfy your needs?
@Phil Stopford (philstopford) please do not change priority yourself, this is triaging task. And please comply with our bug submission requirements, this saves us lots of time! I am way tired of repeating this all the time, and then still getting people doing whatever they want here. We don ’t have time to lose on trying to reproduce issues from scratch, .blend file typically saves us at least 5 minutes per report, times tens of report a day… make the math.
Again, I cannot save a blend file because blender instantly crashes when loading the EXR. I get that you're frustrated and consider me to be a contributor to your situation, but I'm genuinely not trying to piss you off here - blender crashes on loading the image. There is no window of opportunity to save a blend file.
@Phil Stopford (philstopford)
Providing a .blend file where this bug can be immediately checked out would be useful:
From the console all I'm getting as an error is:
Error: EXCEPTION_ACCESS_VIOLATION
It also crashes with 2.79 master 5261cd233c0, but it does not crash with 2.80 alpha 4c4aa65adbe in rendered view (although it takes a good while to load the texture), but it crashes eventually if I start toggling views and especially use the LookDev view.
I guess it runs out of memory as the image has an absurd resolution (43000x14000 pixels).
You can save a .blend file of whatever stage you're at before loading the image that causes the crash. So after "Load white.png into the diffuse color slot. Engage viewport, render. Blender will be fine.". The point is to not have developers recreate the conditions by themselves, you can save valuable time by providing a .blend file where they just have to load the image that crashes Blender.
OK. I didn't realize that the time saving was that significant beyond throwing a sphere in; I'll bear that in mind for future reports and apologize for the aggravation caused.
As background, this came up when playing with the cycles_texture_caching branch (which was aligned with master Aug 3). That permits the use of tiled EXRs, but blender crashes with the EXR images. I'd hoped to use the simplify (viewport texture) parameter to avoid the crash, but that doesn't avoid the crash. I'm somewhat surprised that the PNG doesn't result in a crash.
These large textures come into play for satellite imagery where far away to close up transitions are desired, also for landscapes. The crash seems to occur even with the viewport not set to show any textures, which puzzled me as well.
Crash happens in OIIO library itself, not much we can do here (bsides updating the lib, which is currently ongoing process).
602 Mega pixel floating point image is just too big, would indeed require very specific handling, this is not supported by Blender currently (unless maybe on some workstation with 64GB ram or so). Even basic exrdisplay command line tool here cannot show it (does not crash, but eats 6.2 GB ram and window cannot show). Pushing software beyond any reasonable limit to make it crash is not really useful…