Crash on maximizing/minimizing UV/Image Editor #39640

New Issue

Jari Aaltonen · 2014-04-08T10:18:24+02:00

Jari Aaltonen commented

2014-04-08 10:18:24 +02:00

System Information
OS X 10.6.8 / ATI Radeon HD 2600

Blender Version
Broken: 2.70 19e627c

Short description of error
Crash while maximizing UV/Image Editor window while rendering.

Exact steps for others to reproduce the error
Crash occurs while rendering with Cycles when maximizing/minimizing UV/Image Editor (showing Render Result) during rendering. Seems to happen when Progressive Refine is enabled. Every other type of window maximizes/minimizes during rendering with no problem.

Happens with every .blend- file.

**System Information** OS X 10.6.8 / ATI Radeon HD 2600 **Blender Version** Broken: 2.70 19e627c **Short description of error** Crash while maximizing UV/Image Editor window while rendering. **Exact steps for others to reproduce the error** Crash occurs while rendering with Cycles when maximizing/minimizing UV/Image Editor (showing Render Result) during rendering. Seems to happen when Progressive Refine is enabled. Every other type of window maximizes/minimizes during rendering with no problem. Happens with every .blend- file.

Jari Aaltonen commented

2014-04-08 10:18:24 +02:00

Changed status to: 'Open'

Jari Aaltonen commented

2014-04-08 10:18:24 +02:00

Added subscriber: @jaalto-3

Willi commented

2014-04-08 11:49:28 +02:00

Added subscriber: @willi-2

Willi commented

2014-04-08 11:49:28 +02:00

Seems to be OS (or system) specific. Didn't experience this in the past and when trying now (yes, progressive refine enabled) on Win7/64, AMD HD 6850 (Catalyst 13.12).

Campbell Barton commented

2014-04-08 14:15:21 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2014-04-08 14:15:21 +02:00

Even if this happens on every file, can you give exact steps to redo this, or upload a file which has the scene setup.

Also try restore factory settings, then try to redo the bug.

Even if this happens on every file, can you give exact steps to redo this, or upload a file which has the scene setup. Also try restore factory settings, then try to redo the bug.

Jari Aaltonen commented

2014-04-08 18:37:53 +02:00

Restored to factory settings. The same occurs.

Okay, It seems that when I lower the bucket size/tile size below 64x64, then crash.

Restored to factory settings. The same occurs. Okay, It seems that when I lower the bucket size/tile size below 64x64, then crash.

Willi commented

2014-04-08 22:00:51 +02:00

Oh, yes, now I succeeded in reproducing it. Had to set tile size to 16x16 and had to maximize/restore several times. I could post the stacktrace, but without debug symbols it doesn't say a lot. I was also not able to reproduce it without progressive refine.

EDIT: I do not even have to open the render result in the image editor to make it crash, but it must be the image editor that is being maximized/restored.

Oh, yes, now I succeeded in reproducing it. Had to set tile size to 16x16 and had to maximize/restore several times. I could post the stacktrace, but without debug symbols it doesn't say a lot. I was also not able to reproduce it without progressive refine. EDIT: I do not even have to open the render result in the image editor to make it crash, but it must be the image editor that is being maximized/restored.

Campbell Barton commented

2014-04-09 00:01:11 +02:00

@jaalto-3 please post a file which crashes when you press render.

Willi commented

2014-04-09 00:14:49 +02:00

#39640.blend

Open the file, press F12, Press Ctrl+Down and keep the Down key pressed (so that it is always switching between maximized and normal view). Might take few seconds until it crashes.

[#39640.blend](https://archive.blender.org/developer/F84315/T39640.blend) Open the file, press F12, Press Ctrl+Down and keep the Down key pressed (so that it is always switching between maximized and normal view). Might take few seconds until it crashes.

Sergey Sharybin self-assigned this 2014-04-10 17:57:46 +02:00

Sergey Sharybin commented

2014-04-10 17:57:46 +02:00

Seems to be issue caused by mine changes in partial update.