Member chriscox Posted June 13 Member Share Posted June 13 When opening a large model (about 29M faces), 3D Coat 2024 (and 4.9 as well) crashes when application memory usage reaches about 4 Gig. Just before the crash, it displays a rather ridiculous message about increasing VM size in the OS settings (which isn't even possible). This is a 64 bit app, on a 64 bit OS, on a machine with 160 GB of RAM and about 8 TB of free disk space. Full crash reports and a sample file can be provided. Let me know what you need to help debug this issue in your code. --------------------------------------- Process: 3DCoat [13840] Path: /Applications/3DCoat-2024.31/3DCoat.app/Contents/MacOS/3DCoat Identifier: com.Pilgway.-DCoat Version: 2024.31 (1) Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-06-13 15:12:23.3744 -0700 OS Version: macOS 14.6.1 (23G93) Report Version: 12 Bridge OS Version: 8.6 (21P6074) Anonymous UUID: 096D5B68-B94E-63F0-17DD-11136D1F6B88 Time Awake Since Boot: 2300000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [13840] VM Region Info: 0 is not in any region. Bytes before following region: 4467380224 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 10a46d000-10c7de000 [ 35.4M] r-x/r-x SM=COW /Applications/3DCoat-2024.31/3DCoat.app/Contents/MacOS/3DCoat Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_platform.dylib 0x7ff805b67aa9 _platform_bzero$VARIANT$Haswell + 41 1 3DCoat 0x10bf5107f BaseMesh::create(int, int, int) + 75 2 3DCoat 0x10b529146 comms::cMeshContainer::CreateHardsurfaceStaticMesh() + 712 3 3DCoat 0x10aaea7e6 VoxelSculptTool::OpenRawMesh(comms::cMeshContainer*, bool) + 2344 4 3DCoat 0x10aaf02dc VoxelSculptTool::SEL_MESH() + 854 5 3DCoat 0x10a4abaab _ImportForVertexPainting() + 698 6 3DCoat 0x10af368ce coat::Scene::importMesh(char const*, comms::cMat4 const&) + 60 7 3DCoat 0x10bd47233 merge(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) + 42 8 3DCoat 0x10bd47266 merge1() + 36 9 3DCoat 0x10bb20e0e endstack + 72 10 3DCoat 0x10bb20ca8 CallSystemFunctionNative(asCContext*, asCScriptFunction*, void*, unsigned int*, void*, unsigned long&, void*) + 1488 11 3DCoat 0x10b9d2a5c CallSystemFunction(int, asCContext*) + 353 12 3DCoat 0x10b7ddd82 asCContext::ExecuteNext() + 762 13 3DCoat 0x10b7dd7da asCContext::Execute() + 284 14 3DCoat 0x10add1760 Script::Run(int, char const*, bool) + 1066 15 3DCoat 0x10add1aa2 Script::Run(char const*, char const*, bool) + 80 16 3DCoat 0x10add1b8b Script::Run(char const*, bool) + 181 17 3DCoat 0x10c0901ec do_mitem_cmd() + 6140 18 3DCoat 0x10a52860f _tcallback<void>::call() + 175 19 3DCoat 0x10b06aa58 BaseWidget::CallCallbacks(unsigned int) + 730 20 3DCoat 0x10b06faf6 Widgets::ProcessWindowsMessages(tagMSG&) + 932 21 3DCoat 0x10b091539 IntfWidget1::OnButtonDown(int) + 167 22 3DCoat 0x10ad4230e comms::cWidgets::HandleInputEvents() + 1322 23 3DCoat 0x10bab71e8 comms::cMain_OnRender(comms::cRect const&) + 123 24 3DCoat 0x10ad4b25e cMacMain_OneIterationOfMessageLoop() + 2312 25 3DCoat 0x10ad522be main + 22929 26 dyld 0x7ff8057af345 start + 1909 Quote Link to comment Share on other sites More sharing options...
Member chriscox Posted June 15 Author Member Share Posted June 15 Well, at least Blender and MeshLab will open the file. Quote Link to comment Share on other sites More sharing options...
Carlosan Posted June 15 Share Posted June 15 Could you please try this version * ? Could be a memory limit with file size on old versions.https://pilgway.com/~sergyi/3DCoat-2024/3DCoat-2025.06.dmg * this version overwrite the vs.2024. Quote Link to comment Share on other sites More sharing options...
Member chriscox Posted June 15 Author Member Share Posted June 15 That version still has the same bogus message, and identical crash. This appears to be a long standing bug in the code (and I'm guessing it's more than one bug). Where would you like me to send the file that reproduces this crash? ------------------------------------- Process: 3DCoat [35767] Path: /Applications/3DCoat-2025.06/3DCoat.app/Contents/MacOS/3DCoat Identifier: com.Pilgway.-DCoat Version: 2025.06 (1) Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-06-15 16:51:51.8420 -0700 OS Version: macOS 14.6.1 (23G93) Report Version: 12 Bridge OS Version: 8.6 (21P6074) Anonymous UUID: 096D5B68-B94E-63F0-17DD-11136D1F6B88 Time Awake Since Boot: 2500000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [35767] VM Region Info: 0 is not in any region. Bytes before following region: 4522786816 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 10d944000-10fb17000 [ 33.8M] r-x/r-x SM=COW /Applications/3DCoat-2025.06/3DCoat.app/Contents/MacOS/3DCoat Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_platform.dylib 0x7ff805b67aa9 _platform_bzero$VARIANT$Haswell + 41 1 3DCoat 0x10f484d21 BaseMesh::create(int, int, int) + 75 2 3DCoat 0x10ea3208c comms::cMeshContainer::CreateHardsurfaceStaticMesh() + 702 3 3DCoat 0x10dfd58c0 VoxelSculptTool::OpenRawMesh(comms::cMeshContainer*, bool) + 2906 4 3DCoat 0x10dfdb258 VoxelSculptTool::SEL_MESH() + 846 5 3DCoat 0x10d981c10 _ImportForVertexPainting() + 703 6 3DCoat 0x10e454208 coat::Scene::importMesh(char const*, comms::cMat4 const&) + 60 7 3DCoat 0x10f268bcb merge(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) + 42 8 3DCoat 0x10f268bfe merge1() + 36 9 3DCoat 0x10dc125f0 void pybind11::cpp_function::initialize<void (*&)(), void, pybind11::name, pybind11::scope, pybind11::sibling, char [1]>(void (*&)(), void (*)(), pybind11::name const&, pybind11::scope const&, pybind11::sibling const&, char const (&) [1])::'lambda'(pybind11::detail::function_call&)::__invoke(pybind11::detail::function_call&) + 12 10 3DCoat 0x10da702d0 pybind11::cpp_function::dispatcher(_object*, _object*, _object*) + 3980 11 Python 0x112ad01b4 cfunction_call + 52 12 Python 0x112a6aff1 _PyObject_MakeTpCall + 129 13 Python 0x112b99277 _PyEval_EvalFrameDefault + 61255 14 Python 0x112b88fea PyEval_EvalCode + 282 15 Python 0x112c13306 PyRun_StringFlags + 214 16 Python 0x112b8394b builtin_exec + 699 17 Python 0x112ad0b34 cfunction_vectorcall_FASTCALL_KEYWORDS + 68 18 Python 0x112b9917f _PyEval_EvalFrameDefault + 61007 19 Python 0x112b9f280 _PyEval_Vector + 128 20 Python 0x112a6f35f method_vectorcall + 207 21 3DCoat 0x10da72699 pybind11::detail::simple_collector<(pybind11::return_value_policy)1>::call(_object*) const + 21 22 3DCoat 0x10da89181 pybind11::object pybind11::detail::object_api<pybind11::handle>::operator()<(pybind11::return_value_policy)1, char const*&>(char const*&) const + 45 23 3DCoat 0x10da97c1a coat::PyExtensionManager::Command(char const*) + 74 24 3DCoat 0x10f5c495c do_mitem_cmd() + 6384 25 3DCoat 0x10e021499 _tcallback<void>::call() + 177 26 3DCoat 0x10e583f33 BaseWidget::CallCallbacks(unsigned int) + 707 27 3DCoat 0x10e588de3 Widgets::ProcessWindowsMessages(tagMSG&) + 909 28 3DCoat 0x10e5aa8fd IntfWidget1::OnButtonDown(int) + 161 29 3DCoat 0x10e253415 comms::cWidgets::HandleInputEvents() + 1289 30 3DCoat 0x10efce8d6 comms::cMain_OnRender(comms::cRect const&) + 127 31 3DCoat 0x10e25c4b5 cMacMain_OneIterationOfMessageLoop() + 2319 32 3DCoat 0x10e2634e3 main + 22905 33 dyld 0x7ff8057af345 start + 1909 1 Quote Link to comment Share on other sites More sharing options...
Carlosan Posted June 16 Share Posted June 16 Send report crash at support@pilgway.com Thanks Quote Link to comment Share on other sites More sharing options...
SERGYI Posted July 3 Share Posted July 3 In 3DCoat 2025.09 for macOS, I performed the following steps: Voxel Sculpting > the largest sphere > Commands > Res+ four times to create a sphere with 62 million triangles, utilizing 12GB of memory (see the attached screenshot). I was able to save and load this sphere in a file of 535MB in size. Activity Monitor displayed 11.2GB of memory after loading the file. Then I downloaded your "PenHolder2000Blur.obj" and inspected it. 14+ million vertices. 29+ million tris. You cannot directly paint on this model. To make it proper, do: 3DCoat > File > Import > Import for AUTOPO > PenHolder2000Blur.obj > Required Poly Count = 20000 > [V] Bypass Density Painting & Stroke Guides > OK > UV/Mark Seams > Commands/Auto-Map > Bake > Bake w/ Normal Map (Per-Pixel) > OK > OK To quickly paint the model: Windows > Panels > Smart Materials > Paints > paint_metal > OK > OK > Layers > [RMB] VolumeX > Fill Entire Layer Please refer to the attached screenshot for reference. The latest 3DCoat for macOS is always here:https://pilgway.com/~sergyi/links-macOS.html Quote Link to comment Share on other sites More sharing options...
Member chriscox Posted July 3 Author Member Share Posted July 3 Nope, 2025.09 still crashes in exactly the same way, with the same bogus error message, using the exact same steps and file given. I gave you a 100% reproducible bug. Reproduce it, fix the bug, then send me a link to the build that has the fixed code. (though I suspect you will find more than one bug in your code) ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: 3DCoat [94546] Path: /Applications/3DCoat-2025.09/3DCoat.app/Contents/MacOS/3DCoat Identifier: com.Pilgway.-DCoat Version: 2025.09 (1) Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-07-03 12:36:30.2044 -0700 OS Version: macOS 14.6.1 (23G93) Report Version: 12 Bridge OS Version: 8.6 (21P6074) Anonymous UUID: 096D5B68-B94E-63F0-17DD-11136D1F6B88 Time Awake Since Boot: 4000000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [94546] VM Region Info: 0 is not in any region. Bytes before following region: 4332138496 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 102373000-10454b000 [ 33.8M] r-x/r-x SM=COW /Applications/3DCoat-2025.09/3DCoat.app/Contents/MacOS/3DCoat Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_platform.dylib 0x7ff805b67aa9 _platform_bzero$VARIANT$Haswell + 41 1 3DCoat 0x103eb8d35 BaseMesh::create(int, int, int) + 75 2 3DCoat 0x103465a24 comms::cMeshContainer::CreateHardsurfaceStaticMesh() + 702 3 3DCoat 0x102a0450c VoxelSculptTool::OpenRawMesh(comms::cMeshContainer*, bool) + 2906 4 3DCoat 0x102a09ea4 VoxelSculptTool::SEL_MESH() + 846 5 3DCoat 0x1023c70be _ImportOriginalTransform() + 439 6 3DCoat 0x102e834b0 coat::Scene::importMesh(char const*, comms::cMat4 const&) + 60 7 3DCoat 0x103c9c51f merge(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) + 42 8 3DCoat 0x103c9c552 merge1() + 36 9 3DCoat 0x103a6f872 endstack + 72 10 3DCoat 0x103a6f70c CallSystemFunctionNative(asCContext*, asCScriptFunction*, void*, unsigned int*, void*, unsigned long&, void*) + 1484 11 3DCoat 0x103917d04 CallSystemFunction(int, asCContext*) + 357 12 3DCoat 0x10372358e asCContext::ExecuteNext() + 762 13 3DCoat 0x103722f7c asCContext::Execute() + 178 14 3DCoat 0x102d13324 Script::Run(int, char const*, bool) + 1066 15 3DCoat 0x102d13664 Script::Run(char const*, char const*, bool) + 80 16 3DCoat 0x102d1374d Script::Run(char const*, bool) + 181 17 3DCoat 0x103ff88f2 do_mitem_cmd() + 6398 18 3DCoat 0x102a50141 _tcallback<void>::call() + 177 19 3DCoat 0x102fb430f BaseWidget::CallCallbacks(unsigned int) + 707 20 3DCoat 0x102fb91bf Widgets::ProcessWindowsMessages(tagMSG&) + 909 21 3DCoat 0x102fdacd9 IntfWidget1::OnButtonDown(int) + 161 22 3DCoat 0x102c833f9 comms::cWidgets::HandleInputEvents() + 1289 23 3DCoat 0x103a02c4e comms::cMain_OnRender(comms::cRect const&) + 127 24 3DCoat 0x102c8c499 cMacMain_OneIterationOfMessageLoop() + 2319 25 3DCoat 0x102c934c7 main + 22905 26 dyld 0x7ff8057af345 start + 1909 Thread 1: 1 Quote Link to comment Share on other sites More sharing options...
SERGYI Posted July 4 Share Posted July 4 Please read my post carefully and pay attention to the words: "I downloaded your "PenHolder2000Blur.obj" and inspected it. 14+ million vertices. 29+ million tris. You cannot directly paint on this model." Quote Link to comment Share on other sites More sharing options...
Member chriscox Posted July 4 Author Member Share Posted July 4 I did read that. I see no reason for that, or for it to fail to open in any part of your application. You still have a crashing bug in your code, plus a bogus error message, which you haven't bothered to investigate or fix. Fortunately other applications can open that file and work with it. Please, tell one of your senior developers to take a look at the bug - and this conversation. And for goodness sake, don't reply until you have fixed the bugs and tested the fix. You've already done enough damage to your company's reputation. Quote Link to comment Share on other sites More sharing options...
Solution SERGYI Posted July 7 Solution Share Posted July 7 Today, I have rebuilt "3DCoat 2025.09" for macOS:https://pilgway.com/~sergyi/links-macOS.html The rebuild contains a fix from Pilgway developer which allows loading the model "PenHolder2000Blur.obj" using these steps in "3DCoat: 1. Startup dialog > Perform Retopology > Import huge reference mesh 2. File > Import > Import Mesh for Voxelization Quote Link to comment Share on other sites More sharing options...
Member chriscox Posted July 7 Author Member Share Posted July 7 Thank you, the fix appears to be working well. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.