the "Capturing Snapshot" feature is currently quite unusable on my Ubuntu 15.10 box. It proceeds very fast until the progress bar reaches 50~60% and then it takes about an hour or longer to complete the snapshot.I'm using YourKit 2015 build 15078 (64bit)

I need to profile a java process at a certain state. I started the process with the following JVM options:-agentpath:/opt/yourkit/bin/linux-x86-64/libyjpagent.so-Xdebug-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005

Then I connect with IDEA and wait until a breakpoint is reached (only the current thread is suspended) and start capturing snapshot in yourkit.

I noticed that I can't even (re)connect to the process when I stopped at a breakpoint and captured a mem snapshot. When I choose the process from yourkit welcom screen, the message "Connecting to Application..." appears but gets stuck at 0%.

I killed the process and restarted yourkit. Then I could connect but snapshot capturing was slow as before. After a reboot, snapshot capturing is really fast again (few seconds). It seems you're right and the stop at the breakpoint is the cause for the problem.

The log you've sent is from the profiler UI (yjp.sh), but we need the log of the profiled application. The profiler UI only triggers the snapshot, but all real work is done in the agent, so we need to know whether anything goes wrong on the agent side.

By the way, we tried to reproduce the problem but didn't manage to.

Are other threads, i.e. those non-stopped at the breakpoint, active? Do they perform any active computations or are more or less idle? The profiler tries to stop all threads during a memory snapshot capture, but it is not always possible. For example, when the profiled application runs with the debugger, the agent cannot stop threads at all (that's a JVM's limitation). So, if other threads are active during the snapshot capture they may interfere.

the workaround with the method invocation trigger seems to be the best solution for my case to avoid stopping at the breakpoint. The HPROF dump also works fine.

There are several other threads running. They *should* not perform any computations but I am not sure. It's a quite complex application and not my code

/media/Daten is an internal HDD that was used for a windows installation before. It's formatted with NTFS I also have an internal SSD (ext4) - but not enough space for all snapshots.I just changed the snapshot directory to the ssd and cannot reproduce the problem anymore. It seems the NTFS disk was the reason. Sry - I did not remember that the partition was formatted with NTFS ... I should have tried another snapshot directory sooner.