[Fixed] TD freezes while trying to use the OP window

Bugs
1

Having a major hiccup, not sure what when wrong.
There are no dump file produced, during and after lauching TD.
Resource shown on taskmgr that it wasnt hogging the system,
it just remain unresponsive.

Acer Aspire 5755G
Nvidia GT 630m /nvidia driver ver 285.64 / acer support
ACER Aspire BIOS 1.9
video bios 70.08.3C.00.22
Win7 home premium SP1

TouchDesignerFTE : ver 16360/16900/17640

Problem: Program freezes and becomes unresponsive when opening/closing OP window
Reproducible: Always

Thank you for looking into this.
Appreciate much for sharing such a great tool. Cheers.

2

Hardware:

Acer Aspire 5755G
Nvidia GT 630m /nvidia driver ver 285.64 / acer support
ACER Aspire BIOS 1.9
video bios 70.08.3C.00.22
Win7 home premium SP1

Version:

TouchDesigner FTE 007 7601

Dump:

Loading Dump File [C:\Users\foo\Desktop\TouchDesigner.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: *** Invalid ***

  • Symbol loading may be unreliable without a symbol search path. *
  • Use .symfix to have the debugger choose a symbol path. *
  • After setting your symbol path, use .reload to refresh symbol locations. *

Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
Machine Name:
Debug session time: Thu Mar 22 02:38:10.000 2012 (UTC + 8:00)
System Uptime: not available
Process Uptime: 0 days 0:01:38.000
…WARNING: d3d9 overlaps ddraw
…WARNING: propsys overlaps GdiPlus
…WARNING: AudioSes overlaps MMDevAPI
…WARNING: rsaenh overlaps cryptsp
…WARNING: nvapi overlaps quartz
…WARNING: mswsock overlaps comctl32

Cannot read PEB32 from WOW64 TEB32 fffdd000 - Win32 error 0n30
*** ERROR: Symbol file could not be found. Defaulted to export symbols for kernel32.dll -
kernel32!GetProcessAffinityMask+0x2c:
761aa86d 8b45f0 mov eax,dword ptr [ebp-10h] ss:002b:0080c4d8=000000ff

Reproducible: Always

3

We’ve heard a few issues with the 600 series not working so far. Once we get them into the office we can take a look at it but you may just have to wait until a new driver is released.

4

It worked. :smiley: . The latest driver solved the problem.
Awesome.