Created attachment 59027 [details]
Two "zoom out" mouse wheel events before crash
The 3D program blender (http://www.blender.org/) crashes (SIGSEGV) at
various actions when using it with my ThinkPad R50e laptop with a
82852/855GM graphics card (i915 driver). All Blender version from (at least) 2.49b until (at least) 2.62 are affected:
It could be a blender bug, however, I don't think so because
* the exactly same blender version (in hardware accelerated mode) works
with other Debian computers
* blender-softwaregl (supplied with the precompiled blender from the
blender homepage) does not crash.
* It worked with a former version of mesa/i965 on the same machine. I know you want to know which one - it's difficult to tell but it was about two years ago.
I already submitted this issue at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665722 and there detailed system information are available. It happens at least in 7.11 and 8.0.
-- chipset: i686
Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
-- system architecture: 32-bit
-- xf86-video-intel: 2.18.0
-- xserver: X.Org X Server 1.11.4
-- mesa: OpenGL version string: 1.3 Mesa 8.0
-- libdrm: 2.4.30
-- kernel: 3.2.0-2-686-pae
-- Linux distribution: Debian "testing"
-- Machine or mobo model: IBM Thinkpad R50e
-- Display connector: VGA
One possibility to reliably reproduce the bug on my laptop is the
* Start blender with the default scene.
* Add an array modifier to the (preselected) cube.
* Change "count" of the array modifier to 50.
* Use the mouse wheel in the main window to zoom out until all
50 cubes (looking like a big cuboid) can be seen. If this works,
than the system doesn't show the bug. If the application crashes as
soon as the last face of the 50th cube would be shown, you have a
system like mine. See screenshot.
This might be related with https://bugs.freedesktop.org/show_bug.cgi?id=38109
This issuse does not occur anymore, assuming it was fixed in the meantime.
* blender 2.67b
* xorg-server 2:1.12.4-6
* intel module: version 2.19.0 compiled for 220.127.116.112
Suggest to close the bug.
As I opended this report and cannot reproduce the issue anymore with the newer versions, I close it again ;-)