"error reading screen ... file corrupt" in the system console #35175

New Issue

Sanc Tuary · 2013-05-02T02:20:27+02:00

Sanc Tuary commented

2013-05-02 02:20:27 +02:00

%%%--- Operating System, Graphics card ---
winxp 32bits

- Blender version with error, and version that worked ---

\blender-2.66-r56457-win32 from buildbot but i noticed it in a few post 2.66a builds already
Does not happen in stable Blender 2.66a .

- Short description of error ---

When launching Blender after saving my preferences/startup setings, a message "error reading screen ... file corrupt" appears in the Blender system console for every further Blender launch

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Get any recent buildbot version of Blender
Add the folder named " config " in ...\blender2.6rXXXXX\2.66\ (so the startup and user prefs are saved there)
First launch of that specific Blender, the Blender system console find python and does not report any problem
Go to File -> User Preferences and click on the Save User Setting button
Go to File -> Save Startup file and confirm
Quit Blender
Launch Blender again, and see in the Blender system console the message "error reading screen ... file corrupt" will appear (followed by the expected "Read new prefs : ....." and "found bundled python..." normal messages.

It does seem harmless as all the startup and userprefs are loaded correctly, Blender is stable and does not throw any error, and working in Blender is without any problem.
I just report it in case there's something else behind this message that escape me and may cause trouble.%%%

%%%--- Operating System, Graphics card --- winxp 32bits - Blender version with error, and version that worked --- \blender-2.66-r56457-win32 from buildbot but i noticed it in a few post 2.66a builds already Does not happen in stable Blender 2.66a . - Short description of error --- When launching Blender after saving my preferences/startup setings, a message "error reading screen ... file corrupt" appears in the Blender system console for every further Blender launch - Steps for others to reproduce the error (preferably based on attached .blend file) --- - Get any recent buildbot version of Blender - Add the folder named " config " in ...\blender2.6rXXXXX\2.66\ (so the startup and user prefs are saved there) - First launch of that specific Blender, the Blender system console find python and does not report any problem - Go to File -> User Preferences and click on the Save User Setting button - Go to File -> Save Startup file and confirm - Quit Blender - Launch Blender again, and see in the Blender system console the message "error reading screen ... file corrupt" will appear (followed by the expected "Read new prefs : ....." and "found bundled python..." normal messages. It does seem harmless as all the startup and userprefs are loaded correctly, Blender is stable and does not throw any error, and working in Blender is without any problem. I just report it in case there's something else behind this message that escape me and may cause trouble.%%%

Sanc Tuary commented

2013-05-02 02:20:27 +02:00

Changed status to: 'Open'

Sergey Sharybin commented

2013-05-02 10:28:07 +02:00

%%%The same issue happens when you open file from http://projects.blender.org/tracker/?func=detail&atid=498&aid=35182&group_id=9

Could be related on that memory address issue we recently had in startup.blend probably?%%%

%%%The same issue happens when you open file from http://projects.blender.org/tracker/?func=detail&atid=498&aid=35182&group_id=9 Could be related on that memory address issue we recently had in startup.blend probably?%%%

bithunter commented

2013-05-05 21:46:01 +02:00

%%%http://projects.blender.org/tracker/index.php?func=detail&aid=35179&group_id=9&atid=498 might be related.%%%

Sergey Sharybin commented

2013-05-06 14:39:59 +02:00

%%%That was indeed a bug in startup.blend in 2.67-RC, which is fixed now. Unfortunatly, this bug lead to corrupted Compositor screen saved by 32bit RC which makes all releases crash on load. Crash was fixed in svn rev56511 by removing screen if it's corrupted. You'll see messages in the console about this.

Apart from currupted srceen messages happening for files saved by 2.67-RC everything shall be just fine now.

Thanks for the report, and please let us know if you'll notice some issues with builds newer than 56511.%%%

%%%That was indeed a bug in startup.blend in 2.67-RC, which is fixed now. Unfortunatly, this bug lead to corrupted Compositor screen saved by 32bit RC which makes all releases crash on load. Crash was fixed in svn rev56511 by removing screen if it's corrupted. You'll see messages in the console about this. Apart from currupted srceen messages happening for files saved by 2.67-RC everything shall be just fine now. Thanks for the report, and please let us know if you'll notice some issues with builds newer than 56511.%%%

Sergey Sharybin commented

2013-05-06 14:39:59 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2013-05-06 14:39:59 +02:00

Sanc Tuary commented

2013-05-07 09:13:49 +02:00

%%%I tested for a dozen of minutes r56521 (win32) from the buildbot and i confirm the problem seems to be fixed, the "file corrupt" message does not appear after i setup and save my settings, then reload Blender and the compositing layout does not seem to crash anymore after a few seconds.
So far it looks great, thanks.%%%

%%%I tested for a dozen of minutes r56521 (win32) from the buildbot and i confirm the problem seems to be fixed, the "file corrupt" message does not appear after i setup and save my settings, then reload Blender and the compositing layout does not seem to crash anymore after a few seconds. So far it looks great, thanks.%%%

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

"error reading screen ... file corrupt" in the system console #35175