Title: Fatal error when running Code Profiler
Last modified: December 6, 2024

---

# Fatal error when running Code Profiler

 *  [Neven Jevtić](https://wordpress.org/support/users/nevenjevtic/)
 * (@nevenjevtic)
 * [1 year, 5 months ago](https://wordpress.org/support/topic/fatal-error-when-running-code-profiler/)
 * I’m trying to troubleshoot some database performance issues with Code Profiler
   on my site and I’m getting a fatal error due to your plugin.
 *     ```wp-block-code
       Fatal error: Uncaught malkusch\lock\exception\LockAcquireException: Failed to lock the file. in /nas/content/live/asdf/wp-content/plugins/vibes/includes/libraries/lock/mutex/FlockMutex.php:92Stack trace:#0 /nas/content/live/asdf/wp-content/plugins/vibes/includes/libraries/lock/mutex/FlockMutex.php(107): malkusch\lock\mutex\FlockMutex->lockBlocking()#1 /nas/content/live/asdf/wp-content/plugins/vibes/includes/libraries/lock/util/PcntlTimeout.php(88): malkusch\lock\mutex\FlockMutex->malkusch\lock\mutex\{closure}()#2 /nas/content/live/wp-content/plugins/vibes/includes/libraries/lock/mutex/FlockMutex.php(105): malkusch\lock\util\PcntlTimeout->timeBoxed()#3 /nas/content/live/wp-content/plugins/vibes/includes/libraries/lock/mutex/FlockMutex.php(160): malkusch\lock\mutex\FlockMutex->lockPcntl()#4 /nas/content/live/wp-content/plugins/vibes/includes/libraries/lock/mutex/LockMutex.php(43): malkusch\lock\mutex\FlockMutex->lock()#5 /nas/content/live/wp-content/plugins/vibes/includes/features/class-memory.php(122): malkusch\lock\mutex\LockMutex->synchronized()#6 /nas/content/live/wp-content/plugins/vibes/includes/features/class-memory.php(95): Vibes\Plugin\Feature\Memory::write_records_to_memory()#7 /nas/content/live/wp-includes/class-wp-hook.php(322): Vibes\Plugin\Feature\Memory::write()#8 /nas/content/live/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()#9 /nas/content/live/wp-includes/plugin.php(517): WP_Hook->do_action()#10 /nas/content/live/wp-includes/load.php(1280): do_action()#11 [internal function]: shutdown_action_hook()#12 {main}  thrown in /nas/content/live/asdf/wp-content/plugins/vibes/includes/libraries/lock/mutex/FlockMutex.php on line 92
       ```
   
 * Steps to reproduce:
   1. Install Vibes, Decalog, etc.2. Install Code Profiler3.
   Run profiling4. Observe debug logThanks!

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Thread Starter [Neven Jevtić](https://wordpress.org/support/users/nevenjevtic/)
 * (@nevenjevtic)
 * [1 year, 5 months ago](https://wordpress.org/support/topic/fatal-error-when-running-code-profiler/#post-18183802)
 * On staging, I didn’t get an error. However, it turns out that your plugin is 
   the same thing that was causing a slow **Post Save** action.
 * ![](https://i0.wp.com/snipboard.io/Ve97Ns.jpg?ssl=1)
 * ![](https://i0.wp.com/snipboard.io/YIsCMH.jpg?ssl=1)
 * ![](https://i0.wp.com/snipboard.io/s37lTo.jpg?ssl=1)
 *  Thread Starter [Neven Jevtić](https://wordpress.org/support/users/nevenjevtic/)
 * (@nevenjevtic)
 * [1 year, 5 months ago](https://wordpress.org/support/topic/fatal-error-when-running-code-profiler/#post-18202380)
 * Just checking in on this. Would be good to get some feedback that it’s beeing
   noticed.
 * Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Fatal error when running Code Profiler’ is closed to new replies.

 * ![](https://ps.w.org/vibes/assets/icon-256x256.png?rev=2640264)
 * [Vibes](https://wordpress.org/plugins/vibes/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/vibes/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/vibes/)
 * [Active Topics](https://wordpress.org/support/plugin/vibes/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/vibes/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/vibes/reviews/)

 * 2 replies
 * 1 participant
 * Last reply from: [Neven Jevtić](https://wordpress.org/support/users/nevenjevtic/)
 * Last activity: [1 year, 5 months ago](https://wordpress.org/support/topic/fatal-error-when-running-code-profiler/#post-18202380)
 * Status: not resolved