Skip to main content
R.Silva
Known Participant
December 20, 2015
Answered

unbalanced unlock ( 7 :: 40 )

  • December 20, 2015
  • 31 replies
  • 277130 views

Hi:

I just got an error that displays and doesn't want to go away even after I click the only OK button in the dialog box.

The error as cryptic as this is, is:

"After Effects error : unbalanced unlock. ( 7 :: 40 )

Does anybody know how to get rid of this and why did it show up in the first place?

Using Mac OSX El Capitan with the latest AECC2015 update (13.6.1.6)

Thanks.

    This topic has been closed for replies.
    Correct answer kris_cave

    Hey Everyone,

    Just ran into the same thing. I ended up getting rid of it by purging my memory and cache (Edit > Purge > All Memory & Disk Cache...).

    Heads up, I had to be crafty and hit Enter to clear the error then immediately click Edit before the error popped up again.


    Hope this helps!

    31 replies

    Participant
    October 19, 2016

    Yep I am having the same issue while trying to make a mask layer. Even when I restart the program. I restarted the computer even. I only have about 2 minutes to work before the message pops up and I have to force quit the program.

    mikeh64589377
    Participant
    November 10, 2016

    Same error. Contiunally clicked the Enter button while pressing CTRL + Z. Eventually went away withut losing any work.

    deondraj41935267
    Participant
    September 2, 2017

    I cant get around this too, came up while I was copying and pasting keyframes with opacity onto file/layer that was a rendered and converted quicktime. I was making a demo reel for the end of class project. I shot movie with all my little quicktime converted files and other short comps in it. Then I was fading in and out the type titles  copy copying and pasting two opacity keyframes onto my text title laters. When I tried to move past a converted quickitme file that was on a layer in the timeline panel, thats when that (7::40) error popped up. and I cant get it to go away!!!!!Adobe, you need to have better support or don't release a new version of a program until you work out the bugs that's why cloud sucks now because it's always the latest updated version that hasn't had the bugs worked out or the solutions figured out. Adobe, help out your professionals and students that are paying an arm and leg and devoting themselves to learning these fantastic beautiful amazing programs, by having more trained tech ppl respond to these forums so ppl can get their work done and not get fired or get F's on projects. lol Thank  you!!!!!!!!!!

    _R_H_
    Participant
    October 3, 2016

    It must have to do with masking somehow... I just got the same issue here while drawing a path layer. Win 10, Latest CC2015.3
    Wish Adobe would chime in right about now.. it's clearly a bug.

    harryk86160331
    Participating Frequently
    September 18, 2016

    same error. cant do anything. have to kill the entire AE process because the OK doesn't work and keeps popping up again lol. i had a solid with optical flares applied to it which i then tracked to a light source, then i moved the light source several time and bam error. i don't think the error can be fixed because this is an intermittent problem with no exact way to reproduce.

    harryk86160331
    Participating Frequently
    September 19, 2016

    Now i got that annoying error again with only dealing with 2 video footages and 3 or 4 duplicates inside a composition

    stib
    Inspiring
    September 14, 2016

    It's happening now to me. I can't get out of the loop with any of the tricks, I've tried hitting escape, putting on the caps lock, hitting the edit menu as soon as I hit return, but no avail, it's in a death spiral.

    Is it just me or is 15.3 the Worst. After Effects. Ever.

    Participating Frequently
    July 26, 2016

    I am mostly posting for documentation.  I received the same error just now with the most recent version of AE CC 2015.3.  All I was doing was editing text and moving it around which doesn't seem like it would be that taxing on the system (iMac 5k 16gb RAM 4 GHz Intel Core i7) I also have 100GB for my cache which was only at 80% at the time.  It would be nice to have an explanation on how to avoid these little errors as they seem to appear randomly but I'm no engineer

    krismortensen​ and magicfxnm8r2​ 's tricks seems to have worked for now. Enter, ESC, Edit, Save. Or just enter and quickly hitting (command + s) or (command + Shift + s) worked to.  Then clearing your cache and reopening the file, the error has since not popped back up. 

    It might just be me but the new AE CC 2015.3 has had a lot of bugs so far and adobe doesn't like to respond to my emails...

    I hope everyone is having a great day!

    - David

    tinamneely
    Participant
    July 29, 2016

    I received the same error when working with a simple shape layer (adjusting opacity and scale). No matter how many times i click "ok" the error message won't go away.

    Participant
    May 7, 2016

    This happened to me in After Effects CC 2015.1 on PC. No matter how many times I hit escape, the error kept

    popping up, preventing me from saving, exiting, and restarting After Effects. I ended up hitting Enter and escape

    alternately very fast. This eventually produced a layer view, which stopped the error, allowed me to save, exit, and

    restart After Effects. Once restarted, the problem went away.

    Participant
    June 1, 2016

    Exactly the same deal. Happened when creating a mask on an adjustment layer. Esc, Enter saved by bacon!

    kris_cave
    kris_caveCorrect answer
    Inspiring
    March 16, 2016

    Hey Everyone,

    Just ran into the same thing. I ended up getting rid of it by purging my memory and cache (Edit > Purge > All Memory & Disk Cache...).

    Heads up, I had to be crafty and hit Enter to clear the error then immediately click Edit before the error popped up again.


    Hope this helps!

    Participating Frequently
    April 5, 2016

    Eeek! Same here - I'd actually rendered a few things (so therefore it wasn't initiated by doing something active within a project) and had been off in Photoshop for a bit and came back to this error. Clicking OK it just popped up again and that was an unending loop until, like Kris, I managed to get a crafty momentary window of a second or two to save and quit.

    Hmmm...

    Interestingly, as part of trying to find a solution (or even definition) to this error I stumbled upon this which is really interesting in a massively geeky way (couldn't find 7 :: 40 there just yet!)

    http://myleniumerrors.com/

    [Link removed - site has now become spam - it used to be a user-created AE error repository - moderator]

    mcidesign
    Participant
    April 2, 2018

    THAT LINK IS SPAM

    DONT CLICK ON IT

    shiznit1994
    Inspiring
    February 26, 2016

    Just had this happen to me, Started a new project. 3 frames in to the work... Was making a Mask.

    You have all my computer data from other posts lol. CC15, up to date, windows 10. had just cleaned the cache since I was starting a new project. I have to force quit the program..

    juanj74768158
    Participant
    February 7, 2016

    Im Having the same problem, I was creating a new solid layer, after creating i hid the layer so that i can do some masking on the original..and as soon as i started masking my first line the error popped up! Any new leads???

    Thans

    fionnaw
    Participant
    January 29, 2016

    I got the same thing.  I was fading out a title and this popped up. When I clicked OK I lost my fade out. Does any know why?

    Thanks!

    Szalam
    Community Expert
    Community Expert
    January 29, 2016

    What is the exact version number of AE you're using?

    What OS number are you using?

    Motiongrapher-KMRkQT
    Known Participant
    March 14, 2016

    I'm getting the same error. I was drawing a few masks using the STROKE native effect in after effects (latest version 13.7.0.124).

    A handful number of AE bugs are around and the updates are far behind fixing them (if not adding more bugs to the list). I never had this much frustration since 2009!


    Dear adobe developers, things should get faster, smoother and better not buggy and worse!