Daz crashing frequently with new release.

OK, this is just insane.

Win11, Ryzen 5950x, 32 Gb RAM, RTX 4070TI Super. Working fine before the update.  Drivers updated.

Yet it's currently a crapshoot if I can get through a render, even a simple one, without Daz crashing. No error report window, it just vanishes. Sometimes I'm not even rendering - I've had it just vanish moving a figure. There's nothing showing in Windows reliability monitor, there's nothing about an app crash in event viewer - as far as windows is concerened, it's just suddenly not there.

Looking at the Daz log files? (Including a bit with me starting it up again to get the log file) -

The "Failed to create a timer" goes on for *quite* a bit. There's no partial render in the temp folder (which I've had to go to with an *occasional* Daz crash.) This ... basically gives me nothing to work with to troubleshoot or fix. (This happened both before and after a driver update for the video card, I should add. This particular crash was on a very simple scene, three figures, simple room, basically a billboard in the back so there's something in the background.)

2024-03-03 05:04:15.580 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:04:21.668 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 23.55% of image converged
2024-03-03 05:04:21.797 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00452 iterations after 804.028 s.
2024-03-03 05:04:50.146 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:05:08.527 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:05:30.483 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:05:35.634 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:05:40.427 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 33.93% of image converged
2024-03-03 05:05:40.563 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00497 iterations after 882.795 s.
2024-03-03 05:05:42.055 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:05:50.521 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:05:56.545 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:06:03.876 [WARNING] :: QEventDispatcher: Failed to create QEventDispatcherWin32 internal window: 1158

2024-03-03 05:06:03.876 [FATAL] :: Qt: INTERNALL ERROR: failed to install GetMessage hook


2024-03-03 05:21:24.328 +++++++++++++++ DAZ Studio 4.22.0.16 starting +++++++++++++++++
2024-03-03 05:21:24.328 [INFO] :: Performing cleanup...
2024-03-03 05:21:24.330 [INFO] :: Release Cycle: General Release
2024-03-03 05:21:24.330 [INFO] :: Platform bits: 64
2024-03-03 05:21:24.330 [INFO] :: Qt Version: 4.8.7
2024-03-03 05:21:24.330 [INFO] :: OpenSubdiv Version: 3.0.0
2024-03-03 05:21:24.330 [INFO] :: Running on Windows 11, Build 22621, Workstation
2024-03-03 05:21:24.330 [INFO] :: CPU Information:
2024-03-03 05:21:24.330 [INFO] ::     CPU String: AuthenticAMD
2024-03-03 05:21:24.330 [INFO] ::     CPU Brand String: AMD Ryzen 9 5950X 16-Core Processor            
2024-03-03 05:21:24.330 [INFO] ::     Cache Line Size = 64
2024-03-03 05:21:24.330 [INFO] ::     L2 Associativity = 6
2024-03-03 05:21:24.330 [INFO] ::     Cache Size = 512
2024-03-03 05:21:24.330 [INFO] ::     Stepping ID = 2
2024-03-03 05:21:24.330 [INFO] ::     Model = 1
2024-03-03 05:21:24.330 [INFO] ::     Family = 15
2024-03-03 05:21:24.330 [INFO] ::     Extended model = 2
2024-03-03 05:21:24.330 [INFO] ::     Extended family = 10
2024-03-03 05:21:24.331 [INFO] ::     CLFLUSH cache line size = 64
2024-03-03 05:21:24.331 [INFO] ::     APIC Physical ID = 12

 

Digging back, there's a small break with this:

2024-03-03 05:03:08.545 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:03:08.633 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 15.62% of image converged
2024-03-03 05:03:08.766 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00411 iterations after 730.997 s.
2024-03-03 05:03:10.203 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)

 

And scrolling back through what, if printed, would be *pages* of the "failed to create timer" message, it seems to start here:

 

2024-03-03 04:56:44.574 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00193 iterations after 346.805 s.
2024-03-03 04:57:18.618 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00212 iterations after 380.849 s.
2024-03-03 04:57:55.336 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00233 iterations after 417.567 s.
2024-03-03 04:58:35.908 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 1.22% of image converged
2024-03-03 04:58:36.057 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00256 iterations after 458.288 s.
2024-03-03 04:59:19.874 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00281 iterations after 502.105 s.
2024-03-03 05:00:09.031 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 3.45% of image converged
2024-03-03 05:00:09.154 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00309 iterations after 551.385 s.
2024-03-03 05:01:02.509 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:01:03.463 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:01:03.558 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 6.00% of image converged
2024-03-03 05:01:03.688 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00340 iterations after 605.919 s.
2024-03-03 05:01:04.815 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)

 

Here's from what I'm assuming is the start of the render.

 

2024-03-03 04:50:56.522 Iray (Scene Update) : Updating environment
2024-03-03 04:50:56.522 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.
2024-03-03 04:50:57.343 Iray (Scene Update) : Updating code
2024-03-03 04:50:57.344 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating compiled material code.
2024-03-03 04:50:57.344 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating compiled environment code.
2024-03-03 04:50:57.344 Iray (Scene Update) : Updating textures
2024-03-03 04:50:57.344 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating material textures.
2024-03-03 04:50:57.349 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment textures.
2024-03-03 04:50:57.349 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating BSDFs.
2024-03-03 04:50:57.349 Iray (Scene Update) : Updating volumes
2024-03-03 04:50:57.349 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating volumes.
2024-03-03 04:50:57.349 Iray (Scene Update) : Updating lens data
2024-03-03 04:50:57.349 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.
2024-03-03 04:50:57.349 Iray (Scene Update) : Updating lights
2024-03-03 04:50:57.349 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.
2024-03-03 04:50:57.349 Iray (Scene Update) : Updating instance topology
2024-03-03 04:50:57.349 Iray (Scene Update) : Updating flags
2024-03-03 04:50:57.349 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.
2024-03-03 04:50:57.350 Iray (Scene Update) : Updating backplate
2024-03-03 04:50:57.350 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.
2024-03-03 04:50:57.350 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating compiled backplate code.
2024-03-03 04:50:57.350 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate textures.
2024-03-03 04:50:57.350 Iray (Scene Update) : Updating decals
2024-03-03 04:50:57.350 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.
2024-03-03 04:50:57.416 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.
2024-03-03 04:50:57.416 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
2024-03-03 04:50:57.555 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled
2024-03-03 04:50:57.555 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.
2024-03-03 04:50:57.589 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing OptiX for CUDA device 0
2024-03-03 04:50:57.770 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):
2024-03-03 04:50:57.770 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info :     CUDA device 0 (NVIDIA GeForce RTX 4070 Ti SUPER)
2024-03-03 04:50:57.770 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
2024-03-03 04:50:57.770 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend progr: CUDA device 0 (NVIDIA GeForce RTX 4070 Ti SUPER): Processing scene...
2024-03-03 04:50:57.770 Iray (Scene Access) : Retrieving geometry
2024-03-03 04:50:57.770 Iray (Scene Access) : Retrieving device geometry
2024-03-03 04:50:58.000 Iray (Scene Access) : Retrieving volumes
2024-03-03 04:50:58.000 Iray (Scene Access) : Retrieving textures
2024-03-03 04:51:00.955 Iray (Scene Access) : Retrieving device textures
2024-03-03 04:51:01.107 Iray (Scene Access) : Retrieving flags
2024-03-03 04:51:01.107 Iray (Scene Access) : Retrieving device flags
2024-03-03 04:51:01.107 Iray (Scene Access) : Retrieving lights
2024-03-03 04:51:01.107 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : Importing lights for motion time 0
2024-03-03 04:51:01.107 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : Initializing light hierarchy.
2024-03-03 04:51:01.108 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : Light hierarchy initialization took 0.001 s
2024-03-03 04:51:01.109 Iray (Scene Access) : Retrieving device lights
2024-03-03 04:51:01.109 Iray (Scene Access) : Retrieving section objects
2024-03-03 04:51:01.109 Iray (Scene Access) : Retrieving device section objects
2024-03-03 04:51:01.109 Iray (Scene Access) : Retrieving materials
2024-03-03 04:51:01.113 Iray (Scene Access) : Compiling custom code
2024-03-03 04:51:01.129 Iray (Scene Access) : Retrieving environment
2024-03-03 04:51:01.179 Iray (Scene Access) : Retrieving device environment
2024-03-03 04:51:01.214 Iray (Scene Access) : Retrieving backplate
2024-03-03 04:51:01.214 Iray (Scene Access) : Retrieving device backplate
2024-03-03 04:51:01.215 Iray (Scene Access) : Retrieving decals
2024-03-03 04:51:01.215 Iray (Scene Access) : Retrieving device decals
2024-03-03 04:51:01.215 Iray (Scene Access) : Retrieving motion transform data
2024-03-03 04:51:01.215 Iray (Scene Access) : Retrieving device motion transform data
2024-03-03 04:51:01.215 Iray (Scene Access) : Retrieving lens data
2024-03-03 04:51:01.215 Iray (Scene Access) : Retrieving device lens data
2024-03-03 04:51:01.275 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : JIT-linking wavefront kernel in 0.050 s
2024-03-03 04:51:01.281 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 4070 Ti SUPER): Scene processed in 3.512s
2024-03-03 04:51:01.297 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 4070 Ti SUPER): Allocated 759.376 MiB for frame buffer
2024-03-03 04:51:01.297 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 4070 Ti SUPER): Allocated 1.969 GiB of work space (2048k active samples in 0.000s)
2024-03-03 04:51:01.297 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 4070 Ti SUPER): Optimizing for cooperative usage (performance could be sacrificed)
2024-03-03 04:51:03.631 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Allocating 1-layer frame buffer
2024-03-03 04:51:03.981 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00001 iteration after 6.212 s.
2024-03-03 04:51:05.807 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00002 iterations after 8.038 s.
2024-03-03 04:51:07.650 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00003 iterations after 9.881 s.
2024-03-03 04:51:09.485 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00004 iterations after 11.716 s.
2024-03-03 04:51:11.495 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00005 iterations after 13.725 s.
2024-03-03 04:51:13.273 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00006 iterations after 15.503 s.
2024-03-03 04:51:15.117 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00007 iterations after 17.347 s.
2024-03-03 04:51:16.910 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00008 iterations after 19.140 s.
2024-03-03 04:51:18.863 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00009 iterations after 21.093 s.
2024-03-03 04:51:20.623 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00010 iterations after 22.853 s.
2024-03-03 04:51:22.455 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00011 iterations after 24.686 s.
2024-03-03 04:51:26.174 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00013 iterations after 28.405 s.
2024-03-03 04:51:29.704 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00015 iterations after 31.934 s.
2024-03-03 04:51:33.330 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00017 iterations after 35.560 s.
2024-03-03 04:51:36.768 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00019 iterations after 38.999 s.
2024-03-03 04:51:40.411 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00021 iterations after 42.642 s.
2024-03-03 04:51:43.870 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00023 iterations after 46.100 s.
2024-03-03 04:51:47.493 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00025 iterations after 49.723 s.
2024-03-03 04:51:50.948 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00027 iterations after 53.179 s.
2024-03-03 04:51:56.465 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00030 iterations after 58.696 s.
2024-03-03 04:52:01.440 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00033 iterations after 63.671 s.
2024-03-03 04:52:06.798 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00036 iterations after 69.028 s.
2024-03-03 04:52:12.038 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00039 iterations after 74.268 s.
2024-03-03 04:52:19.057 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00043 iterations after 81.288 s.
2024-03-03 04:52:26.043 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00047 iterations after 88.274 s.
2024-03-03 04:52:34.775 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00052 iterations after 97.006 s.
2024-03-03 04:52:43.458 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00057 iterations after 105.689 s.
2024-03-03 04:52:54.043 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00063 iterations after 116.274 s.
2024-03-03 04:53:04.515 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00069 iterations after 126.745 s.
2024-03-03 04:53:16.839 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00076 iterations after 139.070 s.
2024-03-03 04:53:29.244 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00083 iterations after 151.474 s.
2024-03-03 04:53:43.377 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00091 iterations after 165.607 s.
2024-03-03 04:53:59.421 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00100 iterations after 181.652 s.
2024-03-03 04:54:17.284 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00110 iterations after 199.515 s.
2024-03-03 04:54:37.050 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00121 iterations after 219.281 s.
2024-03-03 04:54:58.858 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00133 iterations after 241.088 s.
2024-03-03 04:55:21.379 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00146 iterations after 263.610 s.
2024-03-03 04:55:46.289 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00160 iterations after 288.520 s.
2024-03-03 04:56:14.579 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00176 iterations after 316.810 s.
2024-03-03 04:56:44.574 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00193 iterations after 346.805 s.
2024-03-03 04:57:18.618 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00212 iterations after 380.849 s.
2024-03-03 04:57:55.336 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00233 iterations after 417.567 s.
2024-03-03 04:58:35.908 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 1.22% of image converged
2024-03-03 04:58:36.057 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00256 iterations after 458.288 s.
2024-03-03 04:59:19.874 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00281 iterations after 502.105 s.
2024-03-03 05:00:09.031 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 3.45% of image converged
2024-03-03 05:00:09.154 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00309 iterations after 551.385 s.
2024-03-03 05:01:02.509 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:01:03.463 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
2024-03-03 05:01:03.558 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 6.00% of image converged
2024-03-03 05:01:03.688 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00340 iterations after 605.919 s.
2024-03-03 05:01:04.815 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)

 

 

 

... the heck do I do about this, or is this a "Daz needs to fix it" thing?

«1

Comments

  • felisfelis Posts: 3,666

    I don't think I have ever seen that error: Failed to create a timer

    You said it was a simple scene, but it renders rather slow.

    What happens if you create a new scene and just add a single character and an HDRI - will that render?

  • hellmastershellmasters Posts: 17

    It was not about the render. Daz was actually not crashed or died. The daz process was killed by windows. It don't have to be a render.

     

    If you leave the daz program for hours before returning and click on anything to create an event, the process will be killed by OS.

     

    My log file was actually looked like this.

    2024-03-03 22:35:12.117 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00030 iterations after 3.239 s.
    2024-03-03 22:35:12.118 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.125 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.135 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.140 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.148 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.155 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.163 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.170 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.178 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.185 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.193 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.200 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.208 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.215 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.222 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.230 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.238 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.246 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.252 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.261 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.267 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.276 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.283 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.298 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.301 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00033 iterations after 3.423 s.
    2024-03-03 22:35:12.306 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.321 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.366 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.372 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.381 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.395 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.403 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.410 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.425 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.433 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.441 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.448 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.462 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.478 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.485 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.499 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00036 iterations after 3.621 s.
    2024-03-03 22:35:12.500 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.515 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.530 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.545 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.560 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.569 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.583 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.600 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.605 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.613 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.623 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.623 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.628 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.636 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.643 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.651 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.658 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.667 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.673 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.681 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.688 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 22:35:12.696 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00039 iterations after 3.818 s.
    2024-03-03 22:35:12.697 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)

     

  • Ricochet180Ricochet180 Posts: 38

    OK, trying a few times:

    HDRI, one G8F figure - ran two renders, no problem.

    Posed that figure - no problem.

    Added second figure - no problem.

    Put in Country Kitchen (unfurnished,) had to hide a wall so the camera had a similar view - *very* long render (40ish minutes.) But finished.

    Deleted kitchen. Added third figure - no problem.

    Added ... bah, trying to remember the name, something photo studio, unfurnished (basically a box missing one side.) Took an *hour and a half* to render. Got to 98-99%. Next time I looked over, Daz was completely gone again. 

    Log file has the same thing -

    2024-03-03 09:26:40.280 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:26:40.400 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00160 iterations after 10.540 s.
    2024-03-03 09:26:41.098 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00172 iterations after 11.238 s.
    2024-03-03 09:26:41.178 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:26:42.071 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:26:42.100 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00191 iterations after 12.240 s.
    2024-03-03 09:26:43.268 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00214 iterations after 13.408 s.
    2024-03-03 09:26:44.519 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00239 iterations after 14.659 s.
    2024-03-03 09:26:45.911 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00268 iterations after 16.052 s.
    2024-03-03 09:26:47.499 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00300 iterations after 17.640 s.
    2024-03-03 09:26:49.297 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00336 iterations after 19.436 s.
    2024-03-03 09:26:51.193 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00375 iterations after 21.333 s.
    2024-03-03 09:26:53.310 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00418 iterations after 23.449 s.
    2024-03-03 09:26:55.603 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00465 iterations after 25.743 s.
    2024-03-03 09:26:58.190 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00517 iterations after 28.330 s.
    2024-03-03 09:27:01.008 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00574 iterations after 31.148 s.
    2024-03-03 09:27:04.113 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00637 iterations after 34.253 s.
    2024-03-03 09:27:05.053 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:27:07.144 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:27:07.604 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00706 iterations after 37.745 s.
    2024-03-03 09:27:08.104 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:27:11.223 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00779 iterations after 41.363 s.
    2024-03-03 09:27:15.394 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00862 iterations after 45.534 s.
    2024-03-03 09:27:18.069 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:27:19.032 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:27:19.919 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00952 iterations after 50.058 s.
    2024-03-03 09:27:24.851 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 01050 iterations after 54.991 s.
    2024-03-03 09:27:30.259 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 01159 iterations after 60.399 s.
    2024-03-03 09:27:34.123 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:27:35.119 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:27:36.295 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 01280 iterations after 66.436 s.
    2024-03-03 09:27:42.860 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 01412 iterations after 73.000 s.
    2024-03-03 09:27:47.060 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:27:50.181 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 01558 iterations after 80.321 s.
    2024-03-03 09:27:53.059 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:27:58.174 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 01718 iterations after 88.314 s.
    2024-03-03 09:28:06.907 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 01895 iterations after 97.047 s.
    2024-03-03 09:28:16.659 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 02091 iterations after 106.799 s.
    2024-03-03 09:28:27.314 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 02305 iterations after 117.454 s.
    2024-03-03 09:28:38.082 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:28:39.049 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 02541 iterations after 129.190 s.
    2024-03-03 09:28:51.925 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 02800 iterations after 142.065 s.
    2024-03-03 09:29:06.094 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 03086 iterations after 156.234 s.
    2024-03-03 09:29:20.054 [ERROR] :: QEventDispatcherWin32::registerTimer: Failed to create a timer (The current process has used all of its system allowance of handles for Window Manager objects.)
    2024-03-03 09:29:21.704 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 03401 iterations after 171.845 s.
    2024-03-03 09:29:37.586 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 03721 iterations after 187.726 s.

    I did, at least, get a render in the temp folder (r.jpng) which I wasn't getting before. (Though it's a 52 Mb file, so ... not going to attach that.)  No errors anywhere in Windows logs, reliability monitor, etc.

     

  • Ricochet180Ricochet180 Posts: 38

    hellmasters said:

    It was not about the render. Daz was actually not crashed or died. The daz process was killed by windows. It don't have to be a render.

     

    If you leave the daz program for hours before returning and click on anything to create an event, the process will be killed by OS.

    Problem with that is:

    - I've left it for hours before. Overnight renders, for instance, without this issue, and

    - these are crashing *now.* I'm restarting Daz each time. This last render took an hour and a half, others that have crashed have needed less time.

    So... color me confused.

  • Ricochet180Ricochet180 Posts: 38
    edited March 3

    (Just so the render I *did* get out of the temp directory, with size, can be seen.)

     

    Screenshot 2024-03-03 094455.png
    1259 x 756 - 165K
    Post edited by Ricochet180 on
  • my studio is also crashing randomly since the upgrade

    sometimes during render, sometime on loading assets, sometimes by simply clicking new
    also there s not info in the windows logs, and not even a crash report, as if it simply end the studio

    and the log file is spammed with 

    QEventDispatcherWin32::registerTimer: Failed to create a timer

     

  • PinkusPinkus Posts: 26
    edited March 3

    I am having issues with the interface becoming terribly sluggish after a while, I don't know if it is related.

    With a relatively heavy scene (20 GB without rendering) I had to terminate the process as it got stuck in a state as if it had an open window I could not click (it didn't display it) -- whenever and wherever I clicked it sounded as if I had clicked outside of a pop-up.

    Even with a smaller scene the interface is quite unresponsive, and that is panes navigation, posing is actually faster than selecting a different node.

    Post edited by Pinkus on
  • Dan21Dan21 Posts: 10

    Getting the exact same thing, with the timer error and the program just dissapearing every single time I launch a queue of renders, they've pushed out a completely bugged build.

    And luckily Daz3D are one of the only software distributors in the world who make it impossible to rollback to a prior version when they push out a bugged build without resorting to piracy... there's absolutely no good reason to not have a 4.22.015 download possible when .016 is blatantly bugged but that's this company's customer service for you.

  • Richard HaseltineRichard Haseltine Posts: 96,909

    Dan21 said:

    Getting the exact same thing, with the timer error and the program just dissapearing every single time I launch a queue of renders, they've pushed out a completely bugged build.

    And luckily Daz3D are one of the only software distributors in the world who make it impossible to rollback to a prior version when they push out a bugged build without resorting to piracy... there's absolutely no good reason to not have a 4.22.015 download possible when .016 is blatantly bugged but that's this company's customer service for you.

    How are you queuing, script or plug-in? It isn't a native feature of DS.

  • hellmastershellmasters Posts: 17

    This is not about renderring or queue or anything. The program will just crash after hours of running.

  • Basically, from the way it felt for me and how Daz was eating up memory the longer it was on, there is some process that is activating over and over again in layers until it comes to a halt. I was able to revert, and no longer have that problem, and I'm not going to reinstall it to help troubleshoot it.

  • PinkusPinkus Posts: 26

    I've also noticed some weird message in the progress pop up window while saving, as if it was displaying some tooltip for pane control icons, which I've never seen before in that window. I don't know if it relates to some leaking that causes the slow down of the interface. Btw, just typing the file name was painful...

  • I think this is related to this post. Latest version of Daz locking up when I idle - Daz 3D Forums We seem to be having the same problems. Daz crashing after running a while/idle. I submitted a ticket and exchanged e-mails regarding the issue. The more people that do, the quicker it might get resoleved, hopefullt.

  • Richard HaseltineRichard Haseltine Posts: 96,909

    protosynthetic said:

    Basically, from the way it felt for me and how Daz was eating up memory the longer it was on, there is some process that is activating over and over again in layers until it comes to a halt. I was able to revert, and no longer have that problem, and I'm not going to reinstall it to help troubleshoot it.

    That doesn't mean it isn't a plug-in, rather than DS itself.

  • DraxiswebDraxisweb Posts: 3

    I can't even leave Daz alone for 10 minutes anymore without it just disappearing when I try to do something. Switching view types, adding clothes, hec k just toggling to the surfaces tab is making it shut down. It's almost unusable for me right now!

  • Richard Haseltine said:

    protosynthetic said:

    Basically, from the way it felt for me and how Daz was eating up memory the longer it was on, there is some process that is activating over and over again in layers until it comes to a halt. I was able to revert, and no longer have that problem, and I'm not going to reinstall it to help troubleshoot it.

    That doesn't mean it isn't a plug-in, rather than DS itself.

    How about we look at how many people are having these issues and stop trying to blame the users and everything except Daz, and start assuming that the coding in the update is faulty?

  • PerttiAPerttiA Posts: 9,480

    stripe6499_9253833ae8 said:

    Richard Haseltine said:

    protosynthetic said:

    Basically, from the way it felt for me and how Daz was eating up memory the longer it was on, there is some process that is activating over and over again in layers until it comes to a halt. I was able to revert, and no longer have that problem, and I'm not going to reinstall it to help troubleshoot it.

    That doesn't mean it isn't a plug-in, rather than DS itself.

    How about we look at how many people are having these issues and stop trying to blame the users and everything except Daz, and start assuming that the coding in the update is faulty?

    I don't see Richard blaiming the users, but before the culprit is found, nobody knows what to fix.

    It may be a plugin, nVidia drivers, Windows version, Windows update, some setting in the OS or DS or any combination of these things - Daz needs to find the combination to troubleshoot the problem and the more information can be given to them, the more likely it is for them to find a fix.

  • FishtalesFishtales Posts: 6,043

    I had trouble with the new Studios but I increased the size of the Page File/ Virtual memory on my disc and it went away. I also moved it from the Windows OS disc to another hard drive. with more space.

  • Richard HaseltineRichard Haseltine Posts: 96,909

    PerttiA said:

    stripe6499_9253833ae8 said:

    Richard Haseltine said:

    protosynthetic said:

    Basically, from the way it felt for me and how Daz was eating up memory the longer it was on, there is some process that is activating over and over again in layers until it comes to a halt. I was able to revert, and no longer have that problem, and I'm not going to reinstall it to help troubleshoot it.

    That doesn't mean it isn't a plug-in, rather than DS itself.

    How about we look at how many people are having these issues and stop trying to blame the users and everything except Daz, and start assuming that the coding in the update is faulty?

    I don't see Richard blaiming the users, but before the culprit is found, nobody knows what to fix.

    It may be a plugin, nVidia drivers, Windows version, Windows update, some setting in the OS or DS or any combination of these things - Daz needs to find the combination to troubleshoot the problem and the more information can be given to them, the more likely it is for them to find a fix.

    Exactly, we need to avoid assumptions and gather evidence so that the problem can be identified and fixed (wherever it lies).

  • Richard Haseltine said:

    PerttiA said:

    stripe6499_9253833ae8 said:

    Richard Haseltine said:

    protosynthetic said:

    Basically, from the way it felt for me and how Daz was eating up memory the longer it was on, there is some process that is activating over and over again in layers until it comes to a halt. I was able to revert, and no longer have that problem, and I'm not going to reinstall it to help troubleshoot it.

    That doesn't mean it isn't a plug-in, rather than DS itself.

    How about we look at how many people are having these issues and stop trying to blame the users and everything except Daz, and start assuming that the coding in the update is faulty?

    I don't see Richard blaiming the users, but before the culprit is found, nobody knows what to fix.

    It may be a plugin, nVidia drivers, Windows version, Windows update, some setting in the OS or DS or any combination of these things - Daz needs to find the combination to troubleshoot the problem and the more information can be given to them, the more likely it is for them to find a fix.

    Exactly, we need to avoid assumptions and gather evidence so that the problem can be identified and fixed (wherever it lies).

    Which is why I've spent the week exchanging emails with tech support, reproducing the issue, and sending log files and descriptions of what I've been doing to get these results. As a former sys admin, I have some basic idea of how to trouble shoot to get data, which is what I've been doing, but take a look at the admin posts on these threads, has anyone of them suggested that the issue might be Daz? No, I've seen suggestions that plugins or power saving settings on the OS might be responsible amongst other things, those are assumptioons, assumptiions that we're being cautioned not to make about Daz? But not one admission that Daz MIGHT be the issue. Agreed, it may not be, but at least let's be honest here. The previous version of DS worked fine, the update doesn't. Seems like a good place to start.

  • Richard HaseltineRichard Haseltine Posts: 96,909
    edited March 7

    stripe6499_9253833ae8 said:

    Richard Haseltine said:

    PerttiA said:

    stripe6499_9253833ae8 said:

    Richard Haseltine said:

    protosynthetic said:

    Basically, from the way it felt for me and how Daz was eating up memory the longer it was on, there is some process that is activating over and over again in layers until it comes to a halt. I was able to revert, and no longer have that problem, and I'm not going to reinstall it to help troubleshoot it.

    That doesn't mean it isn't a plug-in, rather than DS itself.

    How about we look at how many people are having these issues and stop trying to blame the users and everything except Daz, and start assuming that the coding in the update is faulty?

    I don't see Richard blaiming the users, but before the culprit is found, nobody knows what to fix.

    It may be a plugin, nVidia drivers, Windows version, Windows update, some setting in the OS or DS or any combination of these things - Daz needs to find the combination to troubleshoot the problem and the more information can be given to them, the more likely it is for them to find a fix.

    Exactly, we need to avoid assumptions and gather evidence so that the problem can be identified and fixed (wherever it lies).

    Which is why I've spent the week exchanging emails with tech support, reproducing the issue, and sending log files and descriptions of what I've been doing to get these results. As a former sys admin, I have some basic idea of how to trouble shoot to get data, which is what I've been doing, but take a look at the admin posts on these threads, has anyone of them suggested that the issue might be Daz? No, I've seen suggestions that plugins or power saving settings on the OS might be responsible amongst other things, those are assumptioons, assumptiions that we're being cautioned not to make about Daz? But not one admission that Daz MIGHT be the issue. Agreed, it may not be, but at least let's be honest here. The previous version of DS worked fine, the update doesn't. Seems like a good place to start.

    The cautions about its potentially being a plug-in or other factor have generally been in repsonse to posts assuming it is the base application. The obvious troubleshooting step, which another user is trying, is to disable the non-core plug-ins and then - assuming the issue goes away - work through those to see which makes it start (or publish a list of disabled plug-ins so others can report if they have them without issue, which would at least provisionally claer them and reduce the number needing testing).

    Disable non-Daz plug-ins http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/plugins/plugins_load_config/start

    Post edited by Richard Haseltine on
  • jodhan322jodhan322 Posts: 9

    Pinkus said:

    I am having issues with the interface becoming terribly sluggish after a while, I don't know if it is related.

    With a relatively heavy scene (20 GB without rendering) I had to terminate the process as it got stuck in a state as if it had an open window I could not click (it didn't display it) -- whenever and wherever I clicked it sounded as if I had clicked outside of a pop-up.

    Even with a smaller scene the interface is quite unresponsive, and that is panes navigation, posing is actually faster than selecting a different node.

    Same here. Sometimes I'm trying to build the scene and it gets sluggish to the point of being unresponsive. 
    During rendering the side panel that tells me iterations freezes too. My last render jusmped 4 iterations to 5000 iterations, after a forty minute render.

  • Do you have the recent Heat plug-in installed? If you don't use it, ditch it and see what happens.

  • Ricochet180Ricochet180 Posts: 38

    All right. I'm tenatively saying it's the HEAT plugin.

    Hadn't been able to do much with it for the last few days (busy with other stuff.) Read some of the comments above and realized, yeah, HEAT was the other "new thing." Disabled it in plugins.

    I've since run several renders, starting with a (rough) recreation of the one I showed before as a test a few times. No crashing, and no trace of that error in the log files today. Even with my current render at about two hours. (Lighting, Moonlight diner, six figures mixed from G3-G9, vehicles with lights and reflective surfaces, so... enough that something should make it upset if it was going to be.)

    Not saying 100% that's the culprit right this moment, but I've done no other updates - OS, driver, etc - since the initial post. Just disabled HEAT plugin.

  • Ricochet180 said:

    All right. I'm tenatively saying it's the HEAT plugin.

    Hadn't been able to do much with it for the last few days (busy with other stuff.) Read some of the comments above and realized, yeah, HEAT was the other "new thing." Disabled it in plugins.

    I've since run several renders, starting with a (rough) recreation of the one I showed before as a test a few times. No crashing, and no trace of that error in the log files today. Even with my current render at about two hours. (Lighting, Moonlight diner, six figures mixed from G3-G9, vehicles with lights and reflective surfaces, so... enough that something should make it upset if it was going to be.)

    Not saying 100% that's the culprit right this moment, but I've done no other updates - OS, driver, etc - since the initial post. Just disabled HEAT plugin.

    guess you might have a point
    had the same issue till i uninstalled the HEAT plugin
    now it seems to work fine again. Heat and Version upgrade came the same day, so...  

  • ExperimenterExperimenter Posts: 162

    Hi, I have a similar problem. Since the Update my installation become slower and slower until it not react anymore. Even the x for closing the window did not work anymore. After reading these posts I deinstalled the HEAT-plugin. I changed a little bit. The time from start to no reaction before was ca. two hours. After the deinstallation it took five to six hours before the programm slowed and stopped.

    Is there something new I can do?

  • I took the heat.dll out of C:\Program Files\DAZ 3D\DAZStudio4\plugins  manually. DIM didn't touch it. Now DAZ seems to be back to normal.I don't know if you'd need to restart DAZ or not since DAZ had crashed yet again right before I did this.

  • MasterstrokeMasterstroke Posts: 1,803

    I don't have any more frequent crashes at all, with the latest release. Simply nothing unexpected, but I didn't get the HEAT plug-in.
    So it might be HEAT causing _your_ issues.

  • VenkasVenkas Posts: 4

    After disabling the HEAT plugin, I was able to save scenes again and Daz Studio 4.22 Pro seems to be stable after a few renders over an hour.

    Before, the longer I had Daz open, the more Daz Studio became unstable.

    Saving would hang up, IRAY would stop previewing, and the Viewport became sluggish. Just scrolling through content became a chore of choppiness.

  • alan bard newcomeralan bard newcomer Posts: 2,106
    edited March 15

    mine has just been stopping in the middle of reading files. 
    As a fun side effect it will not restart unless I restart the system (I love rebooting dual cpus and multiple hard drives and being here to tell windows not to the chkdsk the 12T data drives.)
    but 422. going down also keep 421 from starting from the other drive while 412 doesn't care and will start right up. So I will turn the heat down and see what happens. 
    ---
    so after multiple tries to restart 422 ... and a half hour break it restarts.

    Post edited by alan bard newcomer on
Sign In or Register to comment.