The attached blend file causes Blender to go "not responding" when I do ALT-A.
=====================================
= Blender 2.43 System Information =
=====================================
Platform: win32
========
Python:
======
- Version: 2.4.2 (#46, Nov 17 2005, 20:11:16) [MSC v.1200 32 bit (Intel)]
- Paths:
C:\Program Files\Blender Foundation\Blender
C:\Program Files\Blender Foundation\Blender\python24.zip
.\DLLs
.\lib
.\lib\plat-win
.\lib\lib-tk
C:\Program Files\Blender Foundation\Blender
C:\PROGRA~1\BLENDE~1\Blender
C:\Documents and Settings\martine\Application Data\Blender Foundation\Blender\.blender\scripts
C:\Documents and Settings\martine\Application Data\Blender Foundation\Blender\.blender\scripts\bpymodules
- Directories:
Blender home dir:
C:\Documents and Settings\martine\Application Data\Blender Foundation\Blender\.blender
Default dir for scripts:
C:\Documents and Settings\martine\Application Data\Blender Foundation\Blender\.blender\scripts
Default "bpydata/" data dir for scripts:
C:\Documents and Settings\martine\Application Data\Blender Foundation\Blender\.blender\scripts\bpydata
User defined dir for scripts:
<NOTICE> -- not found
Data dir "bpydata/" inside user defined dir:
<NOTICE> -- not found
Default config data "bpydata/config/" dir:
C:\Documents and Settings\martine\Application Data\Blender Foundation\Blender\.blender\scripts\bpydata\config
- Modules: all basic ones were found.
OpenGL:
======
- Renderer: Intel 915GM
- Vendor: Intel
- Version: 1.4.0 - Build 4.14.10.4410
- Extensions:
GL_ARB_depth_texture GL_ARB_fragment_program GL_ARB_multitexture
GL_ARB_point_parameters GL_ARB_shadow GL_ARB_texture_border_clamp
GL_ARB_texture_compression GL_ARB_texture_cube_map
GL_ARB_texture_env_add GL_ARB_texture_env_combine
GL_ARB_texture_env_dot3 GL_ARB_texture_env_crossbar
GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object
GL_ARB_vertex_program GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra
GL_EXT_blend_color GL_EXT_blend_func_separate GL_EXT_blend_minmax
GL_EXT_blend_subtract GL_EXT_clip_volume_hint
GL_EXT_compiled_vertex_array GL_EXT_cull_vertex
GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_multi_draw_arrays
GL_EXT_packed_pixels GL_EXT_rescale_normal GL_EXT_secondary_color
GL_EXT_separate_specular_color GL_EXT_shadow_funcs
GL_EXT_stencil_two_side GL_EXT_stencil_wrap
GL_EXT_texture_compression_s3tc GL_EXT_texture_env_add
GL_EXT_texture_env_combine GL_EXT_texture_filter_anisotropic
GL_EXT_texture3D GL_3DFX_texture_compression_FXT1
GL_IBM_texture_mirrored_repeat GL_NV_blend_square
GL_NV_texgen_reflection GL_SGIS_generate_mipmap GL_WIN_swap_hint
- Simplistic almost useless benchmark:
Redrawing all areas 10 times took 0.3308 seconds.
..
(*) Found 2 notices, documented in the text above.
Description
Event Timeline
Logged In: YES
user_id=5634
Some more information on the system (do you need any more?):
Processor Intel(R) Pentium(R) M processor 1.73GHz
Processor Speed 1.69 GHz
Memory (RAM) 1024 MB
Operating System Microsoft Windows XP Professional
Operating System Version 5.1.2600
Logged In: YES
user_id=103
Apparently you have on-board intel graphics, which is well known for poor opengl support. I cannot judge if the crash is related to that. You could by tweaking opengl settings (disable all acceleration for example)
Tests with your file in OSX go fine.
Logged In: YES
user_id=5634
The blend works for me on my other box, which has an nVidia card, so I suppose Ton must be right.
Logged In: YES
user_id=103
Too bad to hear this... intel graphics is giving us unpredictable issues all the time.
The only thing we can do is hope for a developer who likes to suffer Intel graphics, and create bypasses or fixes for the most common errors...
Logged In: YES
user_id=5634
I turned off all hardware acceleration and 'write combining', rebooted (to apply the settings), loaded my blend and did ALT-A... no problems.
I turned hardware acceleration back to full, re-enabled 'write combining' etc etc and it hung again as previously.
So it is something to do with the acceleration.
This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.