# Waiting for lock on pidfile .jlassetregistry.lock

**URL:** <https://discourse.julialang.org/t/waiting-for-lock-on-pidfile-jlassetregistry-lock/24962>\
**Category:** General Usage\
**Created:** [June 5, 2019, 1:39pm UTC](https://discourse.julialang.org/t/waiting-for-lock-on-pidfile-jlassetregistry-lock/24962 "2019-06-05T13:39:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bernhard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernhard/32/2619_2.png) [@bernhard](https://discourse.julialang.org/u/bernhard)\
**Post date:** [June 5, 2019, 1:39pm UTC](https://discourse.julialang.org/t/waiting-for-lock-on-pidfile-jlassetregistry-lock/24962/1 "2019-06-05T13:39:04Z")

</div>

A module of mine is using several other modules/packages.  
When I load my module `@everywhere` I get infos about “waiting for lock on pidfile .jlassetregistry.lock”. Can someone help me understand this?  
Can I find out which package is causing this?  
At least once I ran into an error because of this.  
Is there any way I can avoid this info (e.g. should I schedule the `import` on the different workers such that it does not happen in parallel?)

---

<div class="post-metadata">

**Author:** ![bernhard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernhard/32/2619_2.png) [@bernhard](https://discourse.julialang.org/u/bernhard)\
**Post date:** [June 6, 2019, 9:23am UTC](https://discourse.julialang.org/t/waiting-for-lock-on-pidfile-jlassetregistry-lock/24962/2 "2019-06-06T09:23:55Z")

</div>

by opening the json file .jlassetregistry.json in my home folder I could see that PlotyJS and WebIO were causing this (or at least these were the relevant packages). I was able to ‘outsource’ these packages/dependencies to a separate package (which I do not need to load on all workers)