--- Operating System, Graphics card ---
mac os X 10.8.4 built 12E55, NVIDIA GeForce GT 650M on macbook pro Retina, 2.6 Ghz intel core i7
--- Blender version with error, and version that worked ---
Blender 2.68a
--- Short description of error ---
Blender quit unexpectedly.
--- Steps for others to reproduce the error (preferably based on attached .blend file) ---
1- Open Blender 2.68a with factory settings
2- with the mouse ON 3d view use this shortcut to duplicate window CTRL+ALT+W
Description
Event Timeline
I have the exact same MacBook, same OS X version, but couldn't redo the issue with Blender 2.68a.
Is there anything else in your system configuration that may be needed to redo the issue? I can't really think of much, maybe multiple monitors?
Could you try running Blender from the terminal and attach any output that it gives after crashing? The standard command is this, but might be different depending on where you installed Blender:
/Applications/Blender/blender.app/Contents/MacOS/blender
Same problem but I have a 3.41 GHz Intel Quad-Core i7 and an AMD Radeon HD 6850 1024 MB with 8 GB of DDR3 RAM. This problem aroused only very recently.
Hi!
this is the text of terminal:
Last login: Thu Aug 29 10:13:03 on ttys000
mygrvs-MacBook-Pro:~ mygrv$ /Applications/Blender2.68/blender.app/Contents/MacOS/blender
ndof: 3Dx driver not found
Read new prefs: /Users/mygrv/Library/Application Support/Blender/2.68/config/userpref.blend
found bundled python: /Applications/Blender2.68/blender.app/Contents/MacOS/2.68/python
Writing: /tmp/blender.crash.txt
Segmentation fault: 11
and this is the blender.crash.txt file on /tmp
# Blender 2.68 (sub 0), Revision: 58536
# backtrace
0 blender 0x0000000100138884 blender_crash_handler_backtrace + 70
1 blender 0x0000000100138abb blender_crash_handler + 451
2 libsystem_c.dylib 0x00007fff966a194a _sigtramp + 26
3 libobjc.A.dylib 0x00007fff94336005 _ZN4objc8DenseMapIP11objc_objectmLb1ENS_12DenseMapInfoIS2_EENS3_ImEEE4findERKS2_ + 35
Thanks for the log. Unfortunately this log doesn't really give any specific info that could point to the cause. Does the same crash happen in the latest build and older Blender versions?
http://builder.blender.org/download/
http://download.blender.org/release/
Tiny Hammer, is that also on OS X? With the official Blender 2.68a release?
Hi Brecht! Sorry for my bad english.
I try with blender 2.67b but there is no problem with CTRL+ALT+W on 3d view.
OSX 10.8.4
MacPro, dualXeon 16 threads, 24 GB ram, ATI HD 5870.
The official 2.68a and all the newer builds from the buildbot.
I just noticed this report, I already reported (asked I mean) in the BA forum.
I can confirm this. A crash after duplicating window.
But, some more tests.
Enter full screen mode and ask for duplicating windows. Success now.
IMO, such issues are happening on latest OSX builds. There is a serious incompatibility with OSX 10.6.8 and all OSX 10.7x, or 10.8x
There is a plethora of applications - builds around the net, minimum OSX is the 10.7.
Many things changed, and I'm not sure what x code version you are using, what assist apps are you using.
By example, trying aloyr's builds from graphical, such issues may not happening, some other issues though...
Things became complicated for OSX builds.
The official builds are compatible with OSX 10.6.8. OSX full screen mode was not existing there.
On 10.7 or 10.8, run blender in full screen mode. Better!
I get the same crash with 2.68 and 2.68a (OS X 64 bit version). I pick "Duplicate Window" from the Window menu and it crashes immediately. Making a new window by shift-left-clicking on the view corner does not crash, however.
OS X 10.7.5
Mac Pro 1,1
15GB
ATI Radeon HD 5770
I could redo the bug now, fix in svn revision 59962.
If it's still happening, please specify the exact steps to redo the problem. How you make the window fullscreen (shortcut key, menu, fullscreen button on top right of menu), and if Blender already started with the window fullscreen.
It's a bit confusing because we have two fullscreen modes now, the new OS X fullscreen with the button on the top right. Unfortunately that one does not work with multiple screens at all, which is a silly limitation in OS X that I understand will be fixed in 10.9.