crashes when downloading skin materials

[alecjames]

I found the problem reproducible: On windows 10, 20H2 with MH 1.2.0 I tried to download tribal zombies and MH closed without warning. I don’t think there is relevant information in the log file:

[2021-02-21 09:53:26,520] log.py->debug():97 -- DEBUG -- hiding category Modelling
[2021-02-21 09:53:26,520] log.py->debug():97 -- DEBUG -- showing category Community
[2021-02-21 09:53:26,520] log.py->debug():97 -- DEBUG -- hiding task Macro modelling
[2021-02-21 09:53:26,520] log.py->debug():97 -- DEBUG -- showing task Download assets
<<app closed>>
Windows event log:
Faulting application name: pythonw.exe, version: 3.7.6150.1013, time stamp: 0x5dfac7bb
Faulting module name: Qt5Core.dll, version: 5.12.7.0, time stamp: 0x5e2a8d3c
Exception code: 0xc0000409
Fault offset: 0x0000000000028888
Faulting process ID: 0x4788
Faulting application start time: 0x01d7083757f7d40c
Faulting application path: C:\Users\alecj\AppData\Local\makehuman-community\Python\pythonw.exe
Faulting module path: C:\Users\alecj\AppData\Local\makehuman-community\pkgs\PyQt5\Qt\bin\Qt5Core.dll
Report ID: 5af6ba14-6309-4f98-888f-1adfaec214a5
Faulting package full name:
Faulting package-relative application ID:

I hope that’s useful, is it a MH problem?

[joepal]

Unfortunately, it does not crash for me when using the asset downloader to download the tribal zombies skin. This makes it tricky to debug what happens, as I cannot see the internals of the problem.

What I can say is that the material is abnormally large. The included normal map is 59 mb, which is a lot for an image which is only 4096x4096.

This is pure speculation, but maybe the size makes the main thread think the download thread has stalled? Or maybe it overflows a buffer? When downloaded it works as expected inside MH, although its size makes MH take a time to load it.

Only solution I have atm is to avoid this particular asset. Or to download it manually outside the asset downloader, by using a browser and going to the assets link in the menu at the top of this page.

[fake_Person]

I tried downloading it out out the website but it just wont, accept it as a file.
(I have the mhmat in with the images of the skin but makehuman wont let me use it inside the the APP)

[punkduck]

I guess I am late. But I was curious about the size

The normal map is saved as a 16 bit gamma precision png. To make it smaller:

Open Gimp, select Image, then set precision to 8 bit and overwrite it.

4096x4096 now results to 17 mbit

maybe that helps

[RobBaer]

I found the problem reproducible: On windows 10, 20H2 with MH 1.2.0 I tried to download tribal zombies and MH closed without warning. I don’t think there is relevant information in the log file:

[2021-02-21 09:53:26,520] log.py->debug():97 -- DEBUG -- hiding category Modelling
[2021-02-21 09:53:26,520] log.py->debug():97 -- DEBUG -- showing category Community
[2021-02-21 09:53:26,520] log.py->debug():97 -- DEBUG -- hiding task Macro modelling
[2021-02-21 09:53:26,520] log.py->debug():97 -- DEBUG -- showing task Download assets
<<app closed>>
Windows event log:
Faulting application name: pythonw.exe, version: 3.7.6150.1013, time stamp: 0x5dfac7bb
Faulting module name: Qt5Core.dll, version: 5.12.7.0, time stamp: 0x5e2a8d3c
Exception code: 0xc0000409
Fault offset: 0x0000000000028888
Faulting process ID: 0x4788
Faulting application start time: 0x01d7083757f7d40c
Faulting application path: C:\Users\alecj\AppData\Local\makehuman-community\Python\pythonw.exe
Faulting module path: C:\Users\alecj\AppData\Local\makehuman-community\pkgs\PyQt5\Qt\bin\Qt5Core.dll
Report ID: 5af6ba14-6309-4f98-888f-1adfaec214a5
Faulting package full name:
Faulting package-relative application ID:

I hope that’s useful, is it a MH problem?

So this is not exactly solution, but you had a python crash that came from Qt which is a non-MH library used for the MH interface layout. The only time I have experienced frank Python crashes is while Duststorm was first writing the openGL sections of the MH code. At the time these crashes were Windows specific and were extremely hard to track down.

This makes me want to suggest that you double check that your graphics drivers are up to date, and if possible, to try on a different machine that may have a different graphics card. Or, try a Linux or Mac and see if the problem is reproducible on multiple platforms.
Of course, as others have suggested it could be almost anything.