Eagle 8.2.0 bug: file lock mystery

[Anonymous]

lab rat repoirting for duty!

what the actual is going on?

I'm just editing schematyics!

Also: the libraries which were used (all of them) are not stored on project load.

Also annoying as wellk.

[Anonymous]

I think I have seen something like this.   I was editing a board,  and when I tried to close the board app, I got an error that some operation was in progress.  I tried to stop the operation, it didn't work.  Ended up killing the app in the task manager.   😞  

[jorge_garcia]

Hi @Anonymous,

Thanks for your participation. If you work by yourself then the best thing to do is to disable File Locking(Control Panel > Options > Backups/ File Locking). The goal of this feature is to avoid multiple people writing to the same file and destroying each other's changes. It was introduced during the Cadsoft era, and I have found it to be annoying at times. If you go to the location where your board and schematic are saved you'll find .lck files, deleting those will release the lock.

I have included your comments in the existing bug report for File Locking that way the developers can refer to this thread.

Please accept as solution if my post fully resolves or you issue, or reply with additional details if the problem persists.

Please let me know if there's anything else I can do for you.

Best Regards,

[Anonymous]

no .lck files anywhere.
But it got me thinking: Eagle uses stack, right? so there may be stack underrun and overrun?

Easy solution would be to implement incremental numbering version save to the file names. Currently I do it manually, but not often enough. Shadow autosave would increment the smallest version number, the file-project-v0.0.1 ...the regular save button would increment the higher number. Obviously, threre could be much data, but... we have ZIP, TGZ and RAR. Text compresses neatly.

[rachaelATWH4]

---

@Anonymous wrote:

Obviously, threre could be much data, but... we have ZIP, TGZ and RAR. Text compresses neatly.

---

Or just store the deltas from which it can restore the original, much like any modern VCS does or as another example, in enterprise grade software, like how transactions to a database are all logged so things can be restored to the correct point in the event of a failure without losing transactions or getting data out of sync. This would work well with your shadow auto save idea. So the full save pushed the whole new file, the shadow takes a copy and also stores deltas.

[Anonymous]

How do you "resolve" a random error? You can only resolve something that is repeatable or well defined.

Another fun, "text editor" window appears with:

Warning(s):

line 20641: ignoring redefinition of pinref to part 'T1', gate A, pin 'C'

it occurs when I switch from BRD to SCH. that transistor replaced another transistor, the obsolete then deleted. (didn't want to rip up)

[jorge_garcia]

Hi ADresden,

I hope you are doing well, that error is benign and doesnt stop EAGLE from continuing to function. Basically waht it means is that in the XML for that component the same pin withe the exact same name, location, etc pops up twice. Eagle ignores the second copy of the definition.

If you are feeling brave you can go into the XML and remove the extra copy, EAGLE has already given you its location so you have a head start.

Let me know if there is anything else I can do for you.

Best Regards,