ashitsalesforce
commented
2 years ago Hi @StasD,
Based on what you are describing and your experiments, JRE/JDK vendor or version are unlikely to be causing this issue.
What is the CPU architecture of your Mac? Intel x86 or ARM M1/M2?
Look at your system memory to make sure it is not at or near capacity. For example, here is a system whose memory use is near-capacity (14.08GB out of 16GB used). When data loader executes a large job on such a system, the OS starts paging, thereby slowing down responsiveness of data loader to the point where it appears "frozen".
What operation are you performing? If it is not an Export or Export All operation, what's the size of your CSV file? If it is an Export operation, your query result size may be large enough to cause paging due to near-capacity memory use across all running apps and additional heap space usage by data loader to process large extraction result.
If these checks do not help, you can try using jconsole to see data loader's heap space use and whether it is having a full garbage collection (GC). A full GC typically happens either because a java process' maximum allocated heap space is insufficient or because the java process has a memory leak. A tool such as jconsole can help detect occurrences of full GC. To use it, run the command ps -ef | grep swt.nativelib.inpath from command terminal if you are running data loader in interactive (GUI) mode and note down its process id (pid). Next, run jconsole <pid of data loader> to launch JConsole. Here is the screenshot of JConsole attached to a running data loader process:
Here is the screenshot of JConsole with selected "Memory" tab:
You can see that garbage collections (GC) are occurring because of the fluctuations in the memory use. However, a full GCs are not occurring because a full GC usually occurs when the memory use goes to max heap (4.3 Gb in the example above) and then drops.
StasD
Hi, I have an issue with the Dataloader constantly freezing on Mac. Then I have to use "Force Quit" to close it... This can happen at any stage: after I press some button, make a selection, or in between processing batches. Lately I switched to "Bulk API Mode", this seems to have reduced the probability of freezing happening during actual processing, but freezing still can happen at the end during the "verification" stage. Mac OS version is 12.4 (Monterey). Dataloader version is 55.0.1. (Also used 54.0.0 for some time before it, the freezings were happening to it also). As to Java, I have latest versions of JDK 8, 11, and 17 from Oracle installed on my machine, and version 17 was used by the Dataloader, as I understand ("java --version" command in Terminal was returning the info about version 17). Today I was trying to experiment with various java versions: disabled 17, so that 11 was used, then installed the 11 version from Zulu (and disabled 11 from Oracle), nothing helped: the freezings still happen. Can you please tell me at least how can I debug this, to find out what is the underlying issue. Is there an error log somewhere?