Log In
New Account
Home My Page Projects Blender 2.x BF release
Summary Activity Tracker SCM Files

Blender 2.6 Bug Tracker: Browse

[#32358] Gui breaks down while using SSS ui menu

Date:
2012-08-18 18:11
Priority:
3
State:
Closed
Submitted by:
Yigit Savtur (ygtsvtr)
Assigned to:
Brecht Van Lommel (blendix)
Category:
Interface
Status:
Fixed / Closed
Relates to:
Duplicates:
Patches:
 
Summary:
Gui breaks down while using SSS ui menu
Detailed description
While playing with Sub surface scattering settings, the gui brakes, but blender keeps working, i copied the event log it seems there is a problem with cycles gui functions...at least thats what i thought i understood please check the pics and txt file... can supply .blend file but i dont think its related to the file this happend back a month ago or so with another SSS enabled file at another computer at my office... restart fixes it. It happend around mid day and i restarted blender without thinking then i thought i should report this so i followed my steps again to re create it and it did after 2 hours... it activates on materials menu while playing with SSS ui stack and then taking a render (F12).

This bug happend to me before but i didnt take the time to report it, i checked the bugs related to interface but didnt see any related bugs.. so im opening a new one..

Followup

Message
  • Date: 2012-08-21 12:05
  • Sender: Brecht Van Lommel
  • It looks like the python context gets broken here, cycles is the last script that gives the error but there's similar errors from other panels too. There was a fix related to this a few months ago, just after the 2.63 release. So it might be fixed already for 2.64 but this has not been released yet, builds are here though:
    http://download.blender.org/release/

    Could you give me the exact blender version and operating system you used, and verify it in both 2.63 and 2.64?

    I tried working in the UI a bit with SSS materials and doing renders, but could not reproduce the issue. It's likely a threading issue, which means that the time when you click or press buttons affects when it happens. If the bug happens in both versions I'd need to have a .blend file and some exact steps to redo the issue, otherwise it's too difficult to investigate with no way to redo.
  • Date: 2012-08-21 15:40
  • Sender: Yigit Savtur
  • ok i will download the latest test release and see if i can recreate it...

    i was using 2.63 official release, i dont usually use test builds or builds from GSOC (unless i really need it for something)...

    so i will test it for the 2.64 and report back to you....
  • Date: 2012-08-21 15:43
  • Sender: Yigit Savtur
  • sorry forgot the OS and specs...

    Windows 7 64 bit
    AMD Phenom II x6 1100T
    Nvidia 580 GTX
    Gskill Ripjaw 16 gb RAM
  • Date: 2012-08-21 17:59
  • Sender: Yigit Savtur
  • i tried to recreate the bug on 2.64 (2.63.17) and did it 2 times.....
    at 17:06 i tryed and tryed and nothing happened, then i thought what can trigger this so i started to zoom in and zoom out in render window with ctrl+middle mouse button
    and then bug occured... i restarted 2.64 again and after 30 minutes it happened again while i was rolling up and down on the menu with mouse roll.

    after that i restarted and tried until 18:45 but couldnt trigger it again... so i dont have any deffinate answer i an give you on how to recreate it..Sorry i uploaded a new picture
    if you wanna check out i doubt it will help
  • Date: 2012-09-24 19:16
  • Sender: Thomas Dinges
  • Marking this as ToDo, it's too difficult to reproduce and a simple re-start of Blender fixes it.
  • Date: 2012-11-16 21:31
  • Sender: Yigit Savtur
  • This bug has been fixed by Brecht on Revision 52283


    "Python/Context: do not allow any UI context access from threads like render
    or baking. This basically means you will only have access to bpy.data and
    bpy.context.scene, not current window, active object, etc, as those are not
    thread safe anyway and were likely to cause issues already.

    This fixes #30858, where the UI would lose buttons due to context getting
    corrupted when editing objects in pre/post render or using luxrender. The
    context access they did (indirectly) was only using the current scene or
    data so they still work."

    copy of bug is #30858
    Thanks:)
 

Attached Files:

Name Date Download
GUI_crash_log.txt 2012-08-18 18:11 Download
Gui bug.jpg 2012-08-18 18:11 Download

Changes:

Field Old Value Date By
StatusTodo / Closed2012-11-16 21:40blendix
status_idOpen2012-09-24 19:16dingto
close_dateNone2012-09-24 19:16dingto
StatusInvestigate2012-09-24 19:16dingto
StatusNew2012-08-19 01:32campbellbarton
assigned_tonone2012-08-19 01:32campbellbarton
File Added21768: Gui bug.jpg2012-08-18 18:11ygtsvtr
File Added21769: GUI_crash_log.txt2012-08-18 18:11ygtsvtr