DIM crashes at every download attempt

markboylan · June 2013

Prior to DAZ 4.6, DIM was working great for me. Since 4.6 and after updating DIM, DIM works fine right after install, but then crashes on any subsequent download attempt. As a workaround I have been re-installing the new DIM each time, allowing it to open right afterward. I download everything just fine. But then next time I attempt to download it crashes again. Sometimes I get an error message and directions to the "report a bug" process (which has never worked for me). But usually DIM crashes with no notice or warning or error message. The program just closes.

Any downloaded content works fine, and any content updates etc show up in DIM just fine. But download attempts crash DIM.

Any suggestions?

JimmyC_2009 · June 2013

What OS are you using, and is it the latest version of the DIM, 1.0.1.59 that you are using?

When you say it crashes, what exactly are you doing at the time? When you run the Start Queue option, is that when it crashes, and what is the error message exactly?

The DigiVault · June 2013

I download the latest DM and it downloaded one product then fails to log on every time I start it. and shut down.

The DigiVault · June 2013

Sorry, I should have said I'm using windows 7.

markboylan · June 2013

JimmyC_2009 said:
What OS are you using, and is it the latest version of the DIM, 1.0.1.59 that you are using?

When you say it crashes, what exactly are you doing at the time? When you run the Start Queue option, is that when it crashes, and what is the error message exactly?

System:
DIM 1.0.1.59
Windows 7 x64 Service Pack 1 (Log says: Running on Windows 7, Build 7601, Service Pack 1)

Process:
I click the DIM shortcut icon on my desktop. The program opens fine.
I click the “Ready to Download” tab.
All files display there with no issues.
I click the box for a content item to download.
I click “Start Queue.”
The display box for program closes. There is no error message of any kind.
If I again click the DIM shortcut icon on my desktop, nothing happens. Nothing opens, and there is no error or bug message.
If I try to reinstall DIM at that time, I get the error “Waiting for DAZ3DIM to exit.”

I reboot my system.
If I again click the DIM shortcut icon on my desktop, the program opens fine.
This time, however, when I click the “Start Queue” button I get the Install Manager "Fatal Error" box.

InstallManager_error_report_130610-062301

Exception reason
DAZ3DIM.exe caused ACCESS_VIOLATION in module "C:\Program Files (x86)\DAZ 3D\DAZ3DIM1\QtCore4.dll" at 0023:67F51C65, QIODevice::isOpen()+5 byte(s)

I have tried several times to report errors but am unable to create or access an account. The log follows this post.

I completely re-install DIM, clicking the “Open DIM now?” box.

The program will work fine for that session.

But upon re-opening the same cycle as above repeats.

LOG
Platform bits: 32
Qt Version: 4.8.4
Locale: en_US
Running on Windows 7, Build 7601, Service Pack 1
Physical Memory:
Total: 3.9 GB (4294967295)
Avail: 3.9 GB (4294967295)
Virtual Memory:
Total: 3.9 GB (4294836224)
Avail: 3.8 GB (4145709056)
Current Memory Usage: 29%
Current DateTime:
Loc: Mon Jun 10 06:07:19 2013
UTC: Mon Jun 10 12:07:19 2013
Application Data:
Location = C:/Users/Public/Documents/DAZ 3D/InstallManager
Disk Total: 1.8 TB (1987729944576)
Disk Avail: 759.1 GB (815158972416)
Reading dzInstall.ini
Current Account: xxx
Current Download Path:
Location = C:/Program Files (x86)/DAZ 3D/Content
Disk Total: 1.8 TB (1987729944576)
Disk Avail: 759.1 GB (815158972416)
Current Content Install Path:
Location = C:/Users/Public/Documents/My DAZ 3D Library
Disk Total: 1.8 TB (1987729944576)
Disk Avail: 759.1 GB (815158972416)
Current 64-bit Software Install Path:
Location = C:/Program Files
Disk Total: 1.8 TB (1987729944576)
Disk Avail: 759.1 GB (815158972416)
Current 32-bit Software Install Path:
Location = C:/Program Files (x86)
Disk Total: 1.8 TB (1987729944576)
Disk Avail: 759.1 GB (815158968320)
Current Account: xxx
Processed 188 installed products totaling 10.5 GB
Processed 171 products with 290 unique product downloads
WARNING: Could not set permissions on file: C:/Program Files (x86)/DAZ 3D/Content/IM00013439-03_Victoria5PoserCF.zip.part
WARNING: Error opening save file "C:/Program Files (x86)/DAZ 3D/Content/IM00013439-03_Victoria5PoserCF.zip.part" for product 13439-3, "Victoria 5 PoserCF": could not presize file

JimmyC_2009 · June 2013

WARNING: Could not set permissions on file: C:/Program Files (x86)/DAZ 3D/Content/IM00013439-03_Victoria5PoserCF.zip.part
WARNING: Error opening save file “C:/Program Files (x86)/DAZ 3D/Content/IM00013439-03_Victoria5PoserCF.zip.part” for product 13439-3, “Victoria 5 PoserCF”: could not presize file

Why is it looking in Program Files (x86) for a Content folder? Program Files is a protected area, and you should not be storing any user data in there. Do you have a poser runtime folder in there? If so, you would need to move it somewhere else, as Win 7 wont let you write user data into that area.

markboylan · June 2013

JimmyC_2009 said:
WARNING: Could not set permissions on file: C:/Program Files (x86)/DAZ 3D/Content/IM00013439-03_Victoria5PoserCF.zip.part
WARNING: Error opening save file “C:/Program Files (x86)/DAZ 3D/Content/IM00013439-03_Victoria5PoserCF.zip.part” for product 13439-3, “Victoria 5 PoserCF”: could not presize file

Why is it looking in Program Files (x86) for a Content folder? Program Files is a protected area, and you should not be storing any user data in there. Do you have a poser runtime folder in there? If so, you would need to move it somewhere else, as Win 7 wont let you write user data into that area.

I have no idea why files are in that location. When I installed the previous version I used all the defaults. That's where the install program put them. I will try to develop a logical file structure and move everything. Will DAZ autofind those files in their new locations?

JimmyC_2009 · June 2013

Did the DIM install this content? If so, try and get DIM to uninstall it, then reinstall it to the correct library from inside DIM again., that would be the least disruptive way I think.

If DIM wont work, or can't uninstall it, then you would need to move it all yourself into the correct library. If it is a DIM install, then it may mess up your database, but that can be fixed.

JoelLovell · August 2013

I'm having this issue, and I'm using OSX Moutain Lion.

JimmyC_2009 · August 2013

What exact issue are you having, can you please describe it step by step

JoelLovell · August 2013

My Some of the products, after selecting them to download, start to download, then the download failed message comes up. After it does this for a few times, the application crashes. My PC downloads and installs with no problem. Here is the crash report the Mac generates: (note that I had no issues until this last update of the DIM)

Process: DAZ3DIM [911]
Path: /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/MacOS/DAZ3DIM
Identifier: com.DAZ.DAZ3DIM
Version: 1.0 (1.0.1.81)
Code Type: X86 (Native)
Parent Process: launchd [295]
User ID: 501

Date/Time: 2013-08-15 12:03:22.095 -0400
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10

Interval Since Last Report: 98947 sec
Crashes Since Last Report: 6
Per-App Interval Since Last Report: 13834 sec
Per-App Crashes Since Last Report: 6
Anonymous UUID: 9A4125E0-3BB3-5651-A643-F8B4548CA894

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000004e

VM Regions Near 0x4e:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/MacOS/DAZ3DIM
__TEXT 0000000000001000-000000000029d000 [ 2672K] r-x/rwx SM=COW /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/MacOS/DAZ3DIM

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 QtCore 0x0064a8e5 QIODevice::isOpen() const + 9
1 com.DAZ.DAZ3DIM 0x00068436 DzDownloadMgr::finishDownload(bool, QNetworkReply*) + 512
2 com.DAZ.DAZ3DIM 0x0006a666 DzDownloadMgr::setupDownloadFile(QString const&, DzProduct*, DzDownloadReplyInfo*, QString const&, bool) + 3284
3 com.DAZ.DAZ3DIM 0x0006b3db DzDownloadMgr::readDownloadChunk() + 1273
4 com.DAZ.DAZ3DIM 0x0006f3ef DzDownloadMgr::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 577
5 QtCore 0x006ccb61 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1715
6 QtCore 0x00717f27 QIODevice::readyRead() + 49
7 QtNetwork 0x01513f41 QNetworkReplyImplPrivate::appendDownstreamDataSignalEmissions() + 225
8 QtNetwork 0x014fa2f1 QNetworkAccessBackend::writeDownstreamData(QByteDataBuffer&) + 27
9 QtNetwork 0x015031ff QNetworkAccessHttpBackend::replyDownloadData(QByteArray) + 181
10 QtNetwork 0x0157d583 QNetworkAccessHttpBackend::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 443
11 QtCore 0x006c74fc QMetaCallEvent::placeMetaCall(QObject*) + 48
12 QtCore 0x006cbefc QObject::event(QEvent*) + 256
13 QtGui 0x0094658a QApplicationPrivate::notify_helper(QObject*, QEvent*) + 308
14 QtGui 0x0094683e QApplication::notify(QObject*, QEvent*) + 656
15 QtCore 0x006b73e6 QCoreApplication::notifyInternal(QObject*, QEvent*) + 96
16 QtCore 0x006b7813 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 595
17 QtGui 0x00900551 processPostedEvents(QEventDispatcherMacPrivate*, bool) + 321
18 com.apple.CoreFoundation 0x93b8104f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
19 com.apple.CoreFoundation 0x93b80a79 __CFRunLoopDoSources0 + 233
20 com.apple.CoreFoundation 0x93ba6826 __CFRunLoopRun + 934
21 com.apple.CoreFoundation 0x93ba601a CFRunLoopRunSpecific + 378
22 com.apple.CoreFoundation 0x93ba5e8b CFRunLoopRunInMode + 123
23 com.apple.HIToolbox 0x91809f5a RunCurrentEventLoopInMode + 242
24 com.apple.HIToolbox 0x91809cc9 ReceiveNextEventCommon + 374
25 com.apple.HIToolbox 0x91809b44 BlockUntilNextEventMatchingListInMode + 88
26 com.apple.AppKit 0x93fdf93a _DPSNextEvent + 724
27 com.apple.AppKit 0x93fdf16c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
28 com.apple.AppKit 0x93fd55cc -[NSApplication run] + 855
29 QtGui 0x00900c0a QEventDispatcherMac::processEvents(QFlags) + 956
30 QtCore 0x006b4760 QEventLoop::exec(QFlags) + 494
31 QtCore 0x006b7b67 QCoreApplication::exec() + 179
32 com.DAZ.DAZ3DIM 0x0002dceb DzApp::doExec() + 99
33 com.DAZ.DAZ3DIM 0x0002e196 DzApp::run() + 34
34 com.DAZ.DAZ3DIM 0x0009c916 main + 74
35 com.DAZ.DAZ3DIM 0x0002c2e2 start + 54

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x956ea9ae kevent + 10
1 libdispatch.dylib 0x9000bc71 _dispatch_mgr_invoke + 993
2 libdispatch.dylib 0x9000b7a9 _dispatch_mgr_thread + 53

Thread 2:
0 libsystem_kernel.dylib 0x956e9be6 __select + 10
1 QtCore 0x006e0b58 qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) + 56
2 QtCore 0x006e4ab1 QEventDispatcherUNIX::select(int, fd_set*, fd_set*, fd_set*, timeval*) + 45
3 QtCore 0x006e5a18 QEventDispatcherUNIXPrivate::doSelect(QFlags, timeval*) + 1138
4 QtCore 0x006e5e26 QEventDispatcherUNIX::processEvents(QFlags) + 234
5 QtCore 0x006b4760 QEventLoop::exec(QFlags) + 494
6 QtCore 0x005bcb0d QThread::exec() + 203
7 QtCore 0x005bf7eb QThreadPrivate::start(void*) + 381
8 libsystem_c.dylib 0x9a1145b7 _pthread_start + 344
9 libsystem_c.dylib 0x9a0fed4e thread_start + 34

Thread 3:
0 libsystem_kernel.dylib 0x956e9be6 __select + 10
1 QtCore 0x0068ff4c QProcessManager::run() + 250
2 QtCore 0x005bf7eb QThreadPrivate::start(void*) + 381
3 libsystem_c.dylib 0x9a1145b7 _pthread_start + 344
4 libsystem_c.dylib 0x9a0fed4e thread_start + 34

Thread 4:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x956e9be6 __select + 10
1 com.apple.CoreFoundation 0x93bea650 __CFSocketManager + 1632
2 libsystem_c.dylib 0x9a1145b7 _pthread_start + 344
3 libsystem_c.dylib 0x9a0fed4e thread_start + 34

Thread 5:
0 libsystem_kernel.dylib 0x956e9be6 __select + 10
1 QtCore 0x006e0b58 qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) + 56
2 QtCore 0x006e4ab1 QEventDispatcherUNIX::select(int, fd_set*, fd_set*, fd_set*, timeval*) + 45
3 QtCore 0x006e5a18 QEventDispatcherUNIXPrivate::doSelect(QFlags, timeval*) + 1138
4 QtCore 0x006e5e26 QEventDispatcherUNIX::processEvents(QFlags) + 234
5 QtCore 0x006b4760 QEventLoop::exec(QFlags) + 494
6 QtCore 0x005bcb0d QThread::exec() + 203
7 QtCore 0x005bf7eb QThreadPrivate::start(void*) + 381
8 libsystem_c.dylib 0x9a1145b7 _pthread_start + 344
9 libsystem_c.dylib 0x9a0fed4e thread_start + 34

Thread 6:
0 libsystem_kernel.dylib 0x956e9be6 __select + 10
1 QtCore 0x006e0cd8 qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) + 440
2 QtCore 0x006e4ab1 QEventDispatcherUNIX::select(int, fd_set*, fd_set*, fd_set*, timeval*) + 45
3 QtCore 0x006e5a18 QEventDispatcherUNIXPrivate::doSelect(QFlags, timeval*) + 1138
4 QtCore 0x006e5e26 QEventDispatcherUNIX::processEvents(QFlags) + 234
5 QtCore 0x006b4760 QEventLoop::exec(QFlags) + 494
6 QtCore 0x005bcb0d QThread::exec() + 203
7 QtCore 0x005bf7eb QThreadPrivate::start(void*) + 381
8 libsystem_c.dylib 0x9a1145b7 _pthread_start + 344
9 libsystem_c.dylib 0x9a0fed4e thread_start + 34

Thread 7:
0 libsystem_kernel.dylib 0x956e9be6 __select + 10
1 QtCore 0x006e0b58 qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) + 56
2 QtCore 0x006e4ab1 QEventDispatcherUNIX::select(int, fd_set*, fd_set*, fd_set*, timeval*) + 45
3 QtCore 0x006e5a18 QEventDispatcherUNIXPrivate::doSelect(QFlags, timeval*) + 1138
4 QtCore 0x006e5e26 QEventDispatcherUNIX::processEvents(QFlags) + 234
5 QtCore 0x006b4760 QEventLoop::exec(QFlags) + 494
6 QtCore 0x005bcb0d QThread::exec() + 203
7 QtCore 0x005bf7eb QThreadPrivate::start(void*) + 381
8 libsystem_c.dylib 0x9a1145b7 _pthread_start + 344
9 libsystem_c.dylib 0x9a0fed4e thread_start + 34

Thread 8:
0 libsystem_kernel.dylib 0x956ea0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9a1170ac _pthread_workq_return + 45
2 libsystem_c.dylib 0x9a116e79 _pthread_wqthread + 448
3 libsystem_c.dylib 0x9a0fed2a start_wqthread + 30

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000002 ebx: 0x0e2e4468 ecx: 0x002f4180 edx: 0x00144350
edi: 0x0c9dd430 esi: 0x0e29a360 ebp: 0xbfffd858 esp: 0xbfffd858
ss: 0x00000023 efl: 0x00210282 eip: 0x0064a8e5 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x0000004e
Logical CPU: 2

JimmyC_2009 · August 2013

I have asked one of our Mac users to have a look at what you have posted, so hang on

JoelLovell · August 2013

I tried running permissions repairs, re-installing the DIM, but it doesn't make any difference. I may use appzapper and blow it away, then re-try and see what happens.

Totte · August 2013

Hello,

looking at the crash-log from DIM on OSX 10.8.4, it do crash within the receiver socket.
A couple of questions (I've been downloading a lot with the latest DIM on 10.8.4 so there must be something else that causes the crash, something that didn't bother the older version.

A couple of questions?
- What kind of connection do you have? is it reliable or does it tend to drop out now and then?
- Are you running other IP intensive applications on the machine while downloading, like Spotify?

The reason I ask specifically about Spotify is that a client of mine started Spotify in a machine where he was running a program I've developed that uses TCP/IP a lot, and Spotify did some weird things making my program crash deep inside the socket handlers. If he quit Spotify everything worked fine.

JoelLovell · August 2013

I have had on occasion wondered if there is something intermittent about my network, but haven't had anything stand out as conclusive. I'm going to load up some network monitoring tools on my PC and my Mac and see if anything shows up.

I use DropBox, but nothing like Spotify.

Totte · August 2013

jwlovell said:
I have had on occasion wondered if there is something intermittent about my network, but haven't had anything stand out as conclusive. I'm going to load up some network monitoring tools on my PC and my Mac and see if anything shows up.
I use DropBox, but nothing like Spotify.

I use dropbox too on all my machines where I have DIM and I've never seen that do anything bad.
If your network misbehaves, it can cause problems, specially if you have several devices on the way, Switches, routers etc. DIM shouldn't crash though, but it can be deep inside somewhere that you as a programmer don't have any control over.

Post your results.

JoelLovell · August 2013

Still no resolution for my Macbook Pro. DAZ support appears to be throwing their hands up, they simply stated that they can't recreate the problem and are leaving it at that.

I want to manually blow it away completely but my attempts to remove DIM with appzapper must be still leaving some bit somewhere, because after I re-install it, it still has all my login info and settings.

Anyone have any idea?

My network is stable and has no issues. My DIM installations work perfectly on my PC on the same network.

Totte · August 2013

jwlovell said:
Still no resolution for my Macbook Pro. DAZ support appears to be throwing their hands up, they simply stated that they can't recreate the problem and are leaving it at that.
I want to manually blow it away completely but my attempts to remove DIM with appzapper must be still leaving some bit somewhere, because after I re-install it, it still has all my login info and settings.

Anyone have any idea?

My network is stable and has no issues. My DIM installations work perfectly on my PC on the same network.

Appzapper what I know only uses Creator/filetype mapping to track what files belongs to a certain application, which works "about so good".

There are files in /Users/Shared/DAZ 3D

Notifications

DIM crashes at every download attempt

Comments

Adding to Cart…