Followup
| Message |
 |
- Date: 2010-09-01 12:33
- Sender: Colin Litster
- Actually both are back again, temp and temp.001. It appears these are creeping into SVN as a result of someones testing. However, I can't see the point of them in Trunk.
Colin
| - Date: 2010-09-01 12:53
- Sender: Nathan Letwory
- Hmm, these temp and temp.001 are result of opening user preferences in separate window. Trying with a clean build (no previous startup.blend) I cannot find these.
If you have already saved your settings with these temp screen layouts available existing, you'll probably see them always on startup.
Next time when you get this, can you please try changing the area type of user preferences to Info and check if all screen layouts really are gone? You should be able to change there.
I do get a crash when changing user prefs in new window to Info, then try to switch layouts:
ntdll.dll!EtwpCreateEtwThread() + 0x16f1 bytes
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!LdrGetProcedureAddress() + 0x693b bytes
ntdll.dll!RtlRestoreLastWin32Error() + 0x96c bytes
ntdll.dll!EtwEventWriteStartScenario() + 0x123d bytes
ntdll.dll!MD5Final() + 0xb55a bytes
ntdll.dll!RtlRestoreLastWin32Error() + 0x96c bytes
blender.exe!_heap_alloc_base(unsigned __int64 size=252) Line 129 C
blender.exe!_heap_alloc_dbg_impl(unsigned __int64 nSize=200, int nBlockUse=1, const char * szFileName=0x0000000000000000, int nLine=0, int * errno_tmp=0x0000000000b9f820) Line 427 + 0xa bytes C++
blender.exe!_nh_malloc_dbg_impl(unsigned __int64 nSize=200, int nhFlag=0, int nBlockUse=1, const char * szFileName=0x0000000000000000, int nLine=0, int * errno_tmp=0x0000000000b9f820) Line 239 + 0x22 bytes C++
blender.exe!_calloc_dbg_impl(unsigned __int64 nNum=200, unsigned __int64 nSize=200, int nBlockUse=1, const char * szFileName=0x0000000000000000, int nLine=0, int * errno_tmp=0x0000000000b9f820) Line 593 + 0x2c bytes C++
blender.exe!_calloc_dbg(unsigned __int64 nNum=200, unsigned __int64 nSize=1, int nBlockUse=1, const char * szFileName=0x0000000000000000, int nLine=0) Line 644 + 0x2b bytes C++
blender.exe!calloc(unsigned __int64 nNum=200, unsigned __int64 nSize=1) Line 56 + 0x20 bytes C++
> blender.exe!MEM_callocN(unsigned __int64 len=136, const unsigned char * str=0x0000000140e76118) Line 336 + 0x13 bytes C
blender.exe!WM_event_add_keymap_handler(ListBase * handlers=0x00000000032ac4c0, wmKeyMap * keymap=0x00000000031bbc98) Line 1869 + 0x13 bytes C
blender.exe!ed_default_handlers(wmWindowManager * wm=0x0000000003276768, ListBase * handlers=0x00000000032ac4c0, int flag=83) Line 842 C
blender.exe!ED_area_initialize(wmWindowManager * wm=0x0000000003276768, wmWindow * win=0x0000000010677f88, ScrArea * sa=0x00000000032ac268) Line 912 C
blender.exe!ED_screen_refresh(wmWindowManager * wm=0x0000000003276768, wmWindow * win=0x0000000010677f88) Line 1042 C
blender.exe!ED_screen_set(bContext * C=0x0000000000206418, bScreen * sc=0x00000000032a9d08) Line 1309 C
blender.exe!wm_event_do_notifiers(bContext * C=0x0000000000206418) Line 202 C
blender.exe!WM_main(bContext * C=0x0000000000206418) Line 345 C
blender.exe!main(int argc=1, unsigned char * * argv=0x0000000000203010) Line 1164 C
blender.exe!__tmainCRTStartup() Line 266 + 0x19 bytes C
blender.exe!mainCRTStartup() Line 182 C
kernel32.dll!BaseThreadInitThunk() + 0xd bytes
ntdll.dll!RtlUserThreadStart() + 0x21 bytes
| - Date: 2010-09-03 00:09
- Sender: Colin Litster
- Hi Nathan,
That worked to get rid of them but I'm at a loss to know how they kept appearing. I haven't actually changed users preferences for some time, yet temp.001 magically reappeared the other day.
One thing I am regularly doing is compiling and copying the new version over the top of the old. I do this about 4 times a day. In some way could the configuration become corrupted in some way as a result of this copying.
Any sounds like you have found another problem anyway. I'll let you know of any more developments my end.
Cheers
| - Date: 2010-11-01 16:24
- Sender: Kernon Dillon
- I've got 8 of these "temp" screens.
temp ... temp.007
I'm using your builds, Colin, so maybe my temps are linked to your issue? I have changed and saved user prefs several times.
| - Date: 2010-11-09 18:31
- Sender: Ton Roosendaal
- Issue has been solved in today's commit.
| |
|
