a file or module, see Logging for more information. JULIA_PROFILE_PEEK_HEAP_SNAPSHOT Enable collecting of a heap snapshot during execution via the profiling peek mechanism. See Triggered During Execution files (which describe what other projects that your project depends on), and manifest files (which snapshot exact versions of your project's complete dependency graph). One consequence of federation is and line number, plus the complete chain of function calls that led to this line, and hence is a "snapshot" of the current state of execution. If much of your run time is spent executing a particular line

a file or module, see Logging for more information. JULIA_PROFILE_PEEK_HEAP_SNAPSHOT Enable collecting of a heap snapshot during execution via the profiling peek mechanism. See Triggered During Execution files (which describe what other projects that your project depends on), and manifest files (which snapshot exact versions of your project's complete dependency graph). One consequence of federation is and line number, plus the complete chain of function calls that led to this line, and hence is a "snapshot" of the current state of execution. If much of your run time is spent executing a particular line

a file or module, see Logging for more information. JULIA_PROFILE_PEEK_HEAP_SNAPSHOT Enable collecting of a heap snapshot during execution via the profiling peek mechanism. See Triggered During Execution files (which describe what other projects that your project depends on), and manifest files (which snapshot exact versions of your project's complete dependency graph). One consequence of federation is and line number, plus the complete chain of function calls that led to this line, and hence is a "snapshot" of the current state of execution. If much of your run time is spent executing a particular line

a file or module, see Logging for more information. JULIA_PROFILE_PEEK_HEAP_SNAPSHOT Enable collecting of a heap snapshot during execution via the profiling peek mechanism. See Triggered During Execution files (which describe what other projects that your project depends on), and manifest files (which snapshot exact versions of your project's complete dependency graph). One consequence of federation is and line number, plus the complete chain of function calls that led to this line, and hence is a "snapshot" of the current state of execution. If much of your run time is spent executing a particular line

a file or module, see Logging for more information. JULIA_PROFILE_PEEK_HEAP_SNAPSHOT Enable collecting of a heap snapshot during execution via the profiling peek mechanism. See Triggered During Execution files (which describe what other projects that your project depends on), and manifest files (which snapshot exact versions of your project's complete dependency graph). One consequence of federation is and line number, plus the complete chain of function calls that led to this line, and hence is a "snapshot" of the current state of execution. If much of your run time is spent executing a particular line

a file or module, see Logging for more information. JULIA_PROFILE_PEEK_HEAP_SNAPSHOT Enable collecting of a heap snapshot during execution via the profiling peek mechanism. See Triggered During Execution files (which describe what other projects that your project depends on), and manifest files (which snapshot exact versions of your project's complete dependency graph). One consequence of federation is and line number, plus the complete chain of function calls that led to this line, and hence is a "snapshot" of the current state of execution. If much of your run time is spent executing a particular line

a file or module, see Logging for more information. JULIA_PROFILE_PEEK_HEAP_SNAPSHOT Enable collecting of a heap snapshot during execution via the profiling peek mechanism. See Triggered During Execution files (which describe what other projects that your project depends on), and manifest files (which snapshot exact versions of your project's complete dependency graph). One consequence of federation is and line number, plus the complete chain of function calls that led to this line, and hence is a "snapshot" of the current state of execution. If much of your run time is spent executing a particular line

a file or module, see Logging for more information. JULIA_PROFILE_PEEK_HEAP_SNAPSHOT Enable collecting of a heap snapshot during execution via the profiling peek mechanism. See Triggered During Execution files (which describe what other projects that your project depends on), and manifest files (which snapshot exact versions of your project's complete dependency graph). One consequence of federation is and line number, plus the complete chain of function calls that led to this line, and hence is a "snapshot" of the current state of execution. If much of your run time is spent executing a particular line

a file or module, see Logging for more information. JULIA_PROFILE_PEEK_HEAP_SNAPSHOT Enable collecting of a heap snapshot during execution via the profiling peek mechanism. See Triggered During Execution files (which describe what other projects that your project depends on), and manifest files (which snapshot exact versions of your project's complete dependency graph). One consequence of federation is and line number, plus the complete chain of function calls that led to this line, and hence is a "snapshot" of the current state of execution. If much of your run time is spent executing a particular line

a file or module, see Logging for more information. JULIA_PROFILE_PEEK_HEAP_SNAPSHOT Enable collecting of a heap snapshot during execution via the profiling peek mechanism. See Triggered During Execution files (which describe what other projects that your project depends on), and manifest files (which snapshot exact versions of your project's complete dependency graph). One consequence of federation is and line number, plus the complete chain of function calls that led to this line, and hence is a "snapshot" of the current state of execution. If much of your run time is spent executing a particular line