Whenever I run Blender 2.55 64-bit, it instantly closes by itself and all that appears before this happens is a blank console. This started happening with blender 2.54 64-bit, but 2.53 64-bit works perfectly fine. Although the 32-bit versions of each build works perfectly fine and the issue with the 64-bit versions seems to be a recent problem that I hope doesn't go unnoticed for future builds.
Description
Description
Event Timeline
Comment Actions
Could you try starting blender from a cmd.exe and see if there's any output there? Paste that here if you find output.
Comment Actions
I am running windows 7 64-bit and using 2.55 beta and it runs fine. I am using the zip version, not the windows installer.
Comment Actions
David: it would help if you provide more information, we need tangible information we can redo.
Comment Actions
I tried both the zipped and installed versions of the 64-bit releases and neither work. When I try running it through the command prompt i get nothing. I really have no idea why it does this, but I think its worth mentioning that GIMP 2.7 also does this after its launch window finishes loading everything.
Comment Actions
Hrm. This gets hard to test, on both my Windows 7 64bit machines Blender 2.55 and current trunk work fine, both release and debug builds, both 64bit and 32bit builds :/
If GIMP does the same for you too, then maybe it's some environment issue causing the problem?
Closing since I'm unable to redo problem.
Comment Actions
Hey Spencer,
Can you run blender with the -d option from the cmd? (example: blender.exe -d)
maybe it will show you the reason for the crash.
Comment Actions
Both Blender and Gimp use python scripting perhaps you should look there. Try reinstalling or updating your python gtk
Comment Actions
On Windows Blender uses the bundled Python install, so no need to reinstall anything outside of Blender.