Bike hanging and data loss

Bike Outliner
1

I have recently had a few cases of Bike hanging/not responding indefinitely after a few minutes of working on a new outline. I end up having to force-quit, and then Iose everything I wrote.

Today, when I force quit Bike, I took note of the log in case it is helfpul for diagnosis: b5dc495 — paste.sr.ht.

I am wondering if this is a known issue?

Thanks,
Jon

2

Thanks. It might be becoming a known issue… I just got another (first and only other so far report) of similar behavior (but no stack trace) a few days ago.

From your trace the problem seems to be that it hangs while trying to save. Can you remember anything specific about the document state when this problem happens?

  • Have you ever explicitly saved the document to a location before this? Or is it just autosaving to this point?
  • It seems this crash is happening when you do an explicit save… is that correct?
  • Can you reproduce this issue relatively quickly? What steps do you take?
  • Added Also do you have any idea of when crashes might have started? Maybe Console.app > Reports > Crash Reports will contain a list. If so please send me all the Bike ones.

Thanks,
Jesse

1 Like
3

Thanks!

  1. I had not yet saved the file anywhere, so it must have been autosaving.
  2. I think that the app starts to be unresponsive before I attempted to save. The app doesn’t cash, strictly, but just hangs until I force-quit it.
  3. I cannot easily reproduce the issue unfortunately.
  4. I can’t find anything Bike-related in Console.app.

Do let me know if there’s anything else you’d like me to try.

Best,
Jon

4

Next time it happens (before you try to manually save) can you try:

  1. Open Activity Monitor
  2. Select Bike and choose View > Run Spindump

Also if it’s happening at least daily can you try switching back a few releases and see if it stops happening? Maybe can narrow down where the problem originated. I’m looking through code changes now, but not seeing anything that jumps out as possible problem.

Also, anyone else seeing this… noticed any particular origin or cause?

1 Like
5

I think it’s similar to what I encountered before (see the discussion). As far as I can remember, most of the time it happened when I was trying to save the file, but there were likely instances caused by the automatic saving mechanism as well.

In the past two weeks, I encountered a similar situation to @jonsterling’s once. When I switched to Bike from another app (using Command + Tab), I found that it was unresponsive (the spinning beach ball appeared). In the end, I had to force quit the app, and the data was lost.

1 Like
6

In any of these cases is the document open in another app at the same time? For example open also in TextEdit, or being browsed in DevonThink?

Other things:

  • Are you using iCloud Drive with Desktop & Documents Folders syncing?
  • Are you using a third party sync like ChronoSync?

The time I think I’ve seen NSDocument lock up like this was when multiple processes where trying to work on the same document. Depending on the app when that happens they might use a NSFileCoordinator to manage access to the document, and that might get into a bad state. (Maybe have nothing to do with problem), but that’s what I’m wondering about first.

1 Like
7
  1. Document was not open in any other program.
  2. I think I have iCloud Drive with Desktop & Documents folders syncing on that machine, but I am not sure. Will double check when I get back to my office.
  3. No third party sync.
1 Like
8

Any new reports on this problem?

Best guess I have based on stack trace is that there’s another process and Bike trying to access the document file at the same time and and one of them isn’t coordinating right and that causes the lockup. Hard to tell if that’s actually what is happening though. Would love more info or reports on how I can reproduce this.

1 Like
9

Not seeing it here,
but I don’t use iCloud syncing.

1 Like
10

Will definitely let you know what I find when/if this happens next!

1 Like
11

Hi! Today it hung again, but the good thing is that there wasn’t any data loss (I think I’d already successfully saved)! I took a spindump after it started hanging, will email it to you.

Best,
Jon

1 Like