Enabling VBOs in Preferences crashes Blender on exit #42159

Closed
opened 2014-10-09 16:02:49 +02:00 by Riccardo Giovanetti · 16 comments

System Information
Mobile Intel Core i7 720QM (1.66GHz), Win7 Pro 64bit, 8GB RAM, NVIDIA GTS 360M with 1GB VRAM;

Blender Version
Broken: Blender 2.72.1 64bit (Hash: fe93047) (blender-2.72-fe93047-win64.zip) from b.b.o.
Worked: Blender 2.72 64bit (Hash: 95182d1) (blender-2.72-windows64.zip) official release

Short description of error
Enabling VBO in the System Preferences seems to crash Blender when you quit the program.

Exact steps for others to reproduce the error

  1. unpack the zipped installation package in its own dedicated folder (eg. in my case it's D:\Blender\blender-2.72-fe93947-win64 because I use the D:\Blender folder to test versions) (I have Administrator privileges on my local machine and company's network)
  2. before running Blender for the first time add/create also the following folders under the D:\Blender\blender-2.72-fe93947-win64\2.72\ directory along with the others already there (\datafiles; \python and \scripts):
   ... \autosave
   ... \cache
   ... \config
   ... \temp. In this way Blender won't depend on any existing user files and it'll have its own clean environment.

{F115586}pasted_file

  1. Now, run Blender, open the User Preferences, switch to the Files section and change the Temp directory path to the above one you've just added; leave the other settings at their default values for now.
    {F115594}pasted_file

  2. Go to the System section and notice that by default the VBOs checkbox in unselected. Leave it as is, save the Preferences and then save also the Startup File. You'll find these two configuration files inside the ... \config folder.

To test this "presumed bug" start Blender inside the command prompt in Windows 7 (that's my OS) in Debug-All mode to view what's going on. Once Blender starts, move the cube (so you'll be prompted to quit) and quit Blender looking at the terminal console for the messages. When everything works fine you should see the following messages as the last ones:

"...(omissis)
Saved session recovery to 'D:\Blender\blender-2.72-fe93947-win64\2.72\temp\quit.blend'

Blender quit
Press any key to exit ..."
pasted_file
Everything seems fine.

Restart Blender (from command prompt in debug mode), in the System Preferences tick the VBOs checkbox and save the preferences. Now quit Blender. At this point I get the error on exit. With the default startup file the session is saved (quit.blend) but the executable file crashes and an error log file may or may not be created. Instead, when I open an existing project, with the VBOs option activated, Blender may or may not create also a crash log file inside the ...\temp directory; unfortunately the log file is empty.
{F115600}{F115602}{F115604}pasted_file
The above is the only clue I was able to discover after many tests until I found which setting was "apparently" causing the issue. I hope it might help. Thank you for your attention.

P.S.: As suggested by a developer in a bug ticket (I don't remember which one) I also tried to put inside the Blender installation directory the 64bit version of "opengl32.dll" but without any effect apart for an increased lagging of the interface, browsing the menu items and dropdown menu lists, but perhaps it has nothing to do with this "presumed" issue.

**System Information** Mobile Intel Core i7 720QM (1.66GHz), Win7 Pro 64bit, 8GB RAM, NVIDIA GTS 360M with 1GB VRAM; **Blender Version** Broken: Blender 2.72.1 64bit (Hash: fe93047) (blender-2.72-fe93047-win64.zip) from b.b.o. Worked: Blender 2.72 64bit (Hash: 95182d1) (blender-2.72-windows64.zip) official release **Short description of error** Enabling VBO in the System Preferences seems to crash Blender when you quit the program. **Exact steps for others to reproduce the error** 1) unpack the zipped installation package in its own dedicated folder (eg. in my case it's D:\Blender\blender-2.72-fe93947-win64 because I use the D:\Blender folder to test versions) (I have Administrator privileges on my local machine and company's network) 2) before running Blender for the first time add/create also the following folders under the D:\Blender\blender-2.72-fe93947-win64\2.72\ directory along with the others already there (\datafiles; \python and \scripts): ``` ... \autosave ... \cache ... \config ... \temp. In this way Blender won't depend on any existing user files and it'll have its own clean environment. ``` {[F115586](https://archive.blender.org/developer/F115586/pasted_file)}![pasted_file](https://archive.blender.org/developer/F115588/pasted_file) 3) Now, run Blender, open the User Preferences, switch to the Files section and change the Temp directory path to the above one you've just added; leave the other settings at their default values for now. {[F115594](https://archive.blender.org/developer/F115594/pasted_file)}![pasted_file](https://archive.blender.org/developer/F115596/pasted_file) 4) Go to the System section and notice that by default the VBOs checkbox in unselected. Leave it as is, save the Preferences and then save also the Startup File. You'll find these two configuration files inside the ... \config folder. To test this "presumed bug" start Blender inside the command prompt in Windows 7 (that's my OS) in Debug-All mode to view what's going on. Once Blender starts, move the cube (so you'll be prompted to quit) and quit Blender looking at the terminal console for the messages. When everything works fine you should see the following messages as the last ones: "...(omissis) Saved session recovery to 'D:\Blender\blender-2.72-fe93947-win64\2.72\temp\quit.blend' Blender quit Press any key to exit ..." ![pasted_file](https://archive.blender.org/developer/F115598/pasted_file) Everything seems fine. Restart Blender (from command prompt in debug mode), in the System Preferences tick the VBOs checkbox and save the preferences. Now quit Blender. At this point I get the error on exit. With the default startup file the session is saved (quit.blend) but the executable file crashes and an error log file may or may not be created. Instead, when I open an existing project, with the VBOs option activated, Blender may or may not create also a crash log file inside the ...\temp directory; unfortunately the log file is empty. {[F115600](https://archive.blender.org/developer/F115600/pasted_file)}{[F115602](https://archive.blender.org/developer/F115602/pasted_file)}{[F115604](https://archive.blender.org/developer/F115604/pasted_file)}![pasted_file](https://archive.blender.org/developer/F115606/pasted_file) The above is the only clue I was able to discover after many tests until I found which setting was "apparently" causing the issue. I hope it might help. Thank you for your attention. P.S.: As suggested by a developer in a bug ticket (I don't remember which one) I also tried to put inside the Blender installation directory the 64bit version of "opengl32.dll" but without any effect apart for an increased lagging of the interface, browsing the menu items and dropdown menu lists, but perhaps it has nothing to do with this "presumed" issue.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @Harvester

Added subscriber: @Harvester

Added subscriber: @mont29

Added subscriber: @mont29

@Harvester: Is your OS fully up-to-date (drivers and OS all together)?

@Harvester: Is your OS fully up-to-date (drivers and OS all together)?

Hi @mont29, thanks for asking it.

Being in charge of my company's IT infrastructure, servers and clients including my laptop I do manage all the Windows updates via the Windows Server Update Services on the primary domain controller running Windows Server 2008. So, yes, my OS is updated (last update ran on October 1st). The Nvidia graphics card drivers are updated to version 340.52.

Hi @mont29, thanks for asking it. Being in charge of my company's IT infrastructure, servers and clients including my laptop I do manage all the Windows updates via the Windows Server Update Services on the primary domain controller running Windows Server 2008. So, yes, my OS is updated (last update ran on October 1st). The Nvidia graphics card drivers are updated to version 340.52.
Martijn Berger was assigned by Bastien Montagne 2014-10-09 16:56:02 +02:00

Ok, thanks.

Martijn, any idea?

Ok, thanks. Martijn, any idea?

@Harvester might be the same issue as #42166 too, mind checking it?

@Harvester might be the same issue as #42166 too, mind checking it?

I've just tested changing the DPI value, saving preferences, exiting Blender and it doesn't crash. Only when I activate the VBO option Blender crashes on exit.

I've just tested changing the DPI value, saving preferences, exiting Blender and it doesn't crash. Only when I activate the VBO option Blender crashes on exit.

Added subscriber: @DenisBelov

Added subscriber: @DenisBelov

Same behavior here. Win 7x64, GTX 580. However for me it crashes on exit only after rendering and exit. Disabling VBO stoped crashing.

Same behavior here. Win 7x64, GTX 580. However for me it crashes on exit only after rendering and exit. Disabling VBO stoped crashing.

Closed as duplicate of #42166

Closed as duplicate of #42166

Most likely still the same issue.

Most likely still the same issue.

Added subscriber: @JohnWise

Added subscriber: @JohnWise

Fixed with build made on the 17th Hash: 4b42c4b

Fixed with build made on the 17th Hash: 4b42c4b

Hi @JohnWise, I have just downloaded version Hash: 4b42c4b and with the above described closed environment setup it still crashes on exit with the default opening scene at startup (as described above). If I open an existing .blend project file and then exit an empty [blend-filename].crash.txt file is created inside the \temp directory but no application crash error messages are displayed on screen, which lets you believe that Blender closed properly. At least this is what I am experiencing here.

Hi @JohnWise, I have just downloaded version Hash: 4b42c4b and with the above described closed environment setup it still crashes on exit with the default opening scene at startup (as described above). If I open an existing .blend project file and then exit an empty [blend-filename].crash.txt file is created inside the \temp directory but no application crash error messages are displayed on screen, which lets you believe that Blender closed properly. At least this is what I am experiencing here.

Hi @Harvester I just tested the newest version on 2 pc's at work and I still have the same problem here. I'm running on GTX 700 series at work and a GTX 570 at home.

Hi @Harvester I just tested the newest version on 2 pc's at work and I still have the same problem here. I'm running on GTX 700 series at work and a GTX 570 at home.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#42159
No description provided.