Dropbox Sync Hangs on 16-mb "large resource"

Support
1

Version: 1.0.201 (prod, win32)
OS: Windows 10 Education

Hi!

Early this week, I originally set up Joplin and synced with Dropbox fine. Loved the switch from Evernote. But later this week, during a Windows reinstallation, I exported my notes as .JEX, reinstalled Joplin after Windows reinstallation, and imported my notes. However, this time, at around 800 of 8000 items, the lower-left status during syncing would not stay at “Created remote items: 1. Updated remote items: 1.” Every synchronization, it would display this message never moving beyond this item.

I exported my notes, deleted my .config folder and the partial Dropbox backup, and reinstalled Joplin. This time, the problem repeated, but around 3000 of 8000 items. I dug deeper.

This is my log file from the most recent startup and synchronization attempt:

2020-05-02 13:23:54: "Profile directory: C:/Users/David Cole/.config/joplin-desktop"
2020-05-02 13:23:54: "Trying to load 1 master keys..."
2020-05-02 13:23:55: "Loaded master keys: 1"
2020-05-02 13:23:55: "ResourceFetcher: Auto-add resources: Mode: always"
2020-05-02 13:23:55: "ResourceFetcher: Auto-added resources: 0"
2020-05-02 13:23:55: "Trying to load 1 master keys..."
2020-05-02 13:23:55: "Loaded master keys: 1"
2020-05-02 13:23:55: "Scheduling sync operation...", "10000"
2020-05-02 13:23:55: "Trying to load 1 master keys..."
2020-05-02 13:23:55: "Loaded master keys: 1"
2020-05-02 13:23:55: "Scheduling sync operation...", "10000"
2020-05-02 13:23:55: "Trying to load 1 master keys..."
2020-05-02 13:23:55: "Loaded master keys: 1"
2020-05-02 13:23:55: "Scheduling sync operation...", "10000"
2020-05-02 13:23:55: "Scheduling sync operation...", "10000"
2020-05-02 13:23:55: "RevisionService::runInBackground: Starting background service with revision collection interval 600000"
2020-05-02 13:23:56: "DecryptionWorker: starting decryption..."
2020-05-02 13:23:56: "DecryptionWorker: completed decryption."
2020-05-02 13:23:59: "RevisionService::maintenance: Starting..."
2020-05-02 13:23:59: "RevisionService::maintenance: Service is enabled"
2020-05-02 13:23:59: "RevisionService::collectRevisions: Created revisions for 0 notes"
2020-05-02 13:23:59: "RevisionService::maintenance: Done in 118ms"
2020-05-02 13:24:05: "SearchEngine: Updating FTS table..."
2020-05-02 13:24:05: "SearchEngine: Updated FTS table in 1ms. Inserted: 0. Deleted: 0"
2020-05-02 13:24:05: "Saving updated Dropbox auth."
2020-05-02 13:24:05: "Scheduling sync operation...", "0"
2020-05-02 13:24:05: "Preparing scheduled sync"
2020-05-02 13:24:05: "Starting scheduled sync"
2020-05-02 13:24:25: "ResourceService::indexNoteResources: Start"
2020-05-02 13:24:28: "Uploading a large resource (resourceId: 27baf05c16eb413da8a30e9f7417a6b2, size:16412373 bytes) which may tie up the sync process."
2020-05-02 13:24:42: "ResourceService::indexNoteResources: Completed"
2020-05-02 13:24:42: "ResourceService::deleteOrphanResources:", "[]"
2020-05-02 13:28:55: "Running background sync on timer..."
2020-05-02 13:28:55: "Scheduling sync operation...", "0"
2020-05-02 13:28:55: "Preparing scheduled sync"
2020-05-02 13:28:55: "Starting scheduled sync"
2020-05-02 13:28:55: "Synchronisation is already in progress. State: in_progress"
2020-05-02 13:29:01: "SearchEngine: Updating FTS table..."
2020-05-02 13:29:01: "SearchEngine: Updated FTS table in 35ms. Inserted: 1. Deleted: 0"
2020-05-02 13:29:20: "SearchEngine: Updating FTS table..."
2020-05-02 13:29:20: "SearchEngine: Updated FTS table in 31ms. Inserted: 1. Deleted: 0"
2020-05-02 13:29:30: "SearchEngine: Updating FTS table..."
2020-05-02 13:29:31: "SearchEngine: Updated FTS table in 32ms. Inserted: 1. Deleted: 0"
2020-05-02 13:29:42: "SearchEngine: Updating FTS table..."
2020-05-02 13:29:42: "SearchEngine: Updated FTS table in 32ms. Inserted: 1. Deleted: 0"
2020-05-02 13:29:53: "SearchEngine: Updating FTS table..."
2020-05-02 13:29:53: "SearchEngine: Updated FTS table in 39ms. Inserted: 1. Deleted: 0"
2020-05-02 13:33:38: "FetchError: network timeout at: https://content.dropboxapi.com/2/files/upload
FetchError: network timeout at: https://content.dropboxapi.com/2/files/upload
    at C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\node-fetch\index.js:126:13"
2020-05-02 13:33:38: "Operations completed: "
2020-05-02 13:33:38: "createRemote: 1"
2020-05-02 13:33:38: "Total folders: 128"
2020-05-02 13:33:38: "Total notes: 2069"
2020-05-02 13:33:38: "Total resources: 6335"
2020-05-02 13:33:39: "DecryptionWorker: starting decryption..."
2020-05-02 13:33:39: "DecryptionWorker: completed decryption."
2020-05-02 13:33:55: "RevisionService::maintenance: Starting..."
2020-05-02 13:33:55: "RevisionService::maintenance: Service is enabled"
2020-05-02 13:33:55: "RevisionService::collectRevisions: Created revisions for 1 notes"
2020-05-02 13:33:55: "RevisionService::maintenance: Done in 147ms"

It seems to indicate that it is getting suck on a “large file,” but that file is only around 16 MB.

Here is my debugging contents from the last startup and synchronization attempt:

Environment: prod
C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:420 Trying to load a note with no ID - should no longer be possible
UNSAFE_componentWillMount @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:420
C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(HeaderComponent), Connect(MainScreenComponent), Connect(NavigatorComponent), Connect(NoteListComponent), Connect(NoteTextComponent), Connect(RootComponent), Connect(SideBarComponent), Provider
printWarning @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(HeaderComponent), Connect(MainScreenComponent), Connect(NavigatorComponent), Connect(NoteListComponent), Connect(NoteTextComponent), Connect(RootComponent), Connect(SideBarComponent)
printWarning @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(NoteTextViewerComponent), Connect(ToolbarComponent), ReactAce
printWarning @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
lowPriorityWarning @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11513
ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11680
flushRenderPhaseStrictModeWarningsInDEV @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23134
commitRootImpl @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22428
unstable_runWithPriority @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
commitRoot @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22414
runRootCallback @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
scheduleUpdateOnFiber @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21431
enqueueSetState @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:13100
Component.setState @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react\cjs\react.development.js:325
reloadNote @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:637
processTicksAndRejections @ internal/process/task_queues.js:85
async function (async)
reloadNote @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:528
(anonymous) @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:517
setTimeout (async)
scheduleReloadNote @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:516
UNSAFE_componentWillReceiveProps @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:655
callComponentWillReceiveProps @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:13391
updateClassInstance @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:13598
updateClassComponent @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:16992
beginWork$1 @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:18505
beginWork$$1 @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23193
performUnitOfWork @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22208
workLoopSync @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22185
renderRoot @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21878
runRootCallback @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
scheduleUpdateOnFiber @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21431
enqueueSetState @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:13100
Component.setState @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react\cjs\react.development.js:325
onStateChange @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\components\connectAdvanced.js:222
notify @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:30
notifyNestedSubs @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:69
onStateChange @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\components\connectAdvanced.js:219
notify @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:30
notifyNestedSubs @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:69
onStateChange @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\components\connectAdvanced.js:219
dispatch @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\redux\lib\createStore.js:186
generalMiddleware @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:425
generalMiddleware @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\app.js:277
(anonymous) @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:362
refreshNotes @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:323
processTicksAndRejections @ internal/process/task_queues.js:85
async function (async)
refreshNotes @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:278
generalMiddleware @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:493
processTicksAndRejections @ internal/process/task_queues.js:85
Show 23 more frames
C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(NoteTextViewerComponent), Connect(ToolbarComponent)
printWarning @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
lowPriorityWarning @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11513
ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11686
flushRenderPhaseStrictModeWarningsInDEV @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23134
commitRootImpl @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22428
unstable_runWithPriority @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
commitRoot @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22414
runRootCallback @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
scheduleUpdateOnFiber @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21431
enqueueSetState @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:13100
Component.setState @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react\cjs\react.development.js:325
reloadNote @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:637
processTicksAndRejections @ internal/process/task_queues.js:85
async function (async)
reloadNote @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:528
(anonymous) @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:517
setTimeout (async)
scheduleReloadNote @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:516
UNSAFE_componentWillReceiveProps @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:655
callComponentWillReceiveProps @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:13391
updateClassInstance @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:13598
updateClassComponent @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:16992
beginWork$1 @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:18505
beginWork$$1 @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23193
performUnitOfWork @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22208
workLoopSync @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22185
renderRoot @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21878
runRootCallback @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
scheduleUpdateOnFiber @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21431
enqueueSetState @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:13100
Component.setState @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react\cjs\react.development.js:325
onStateChange @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\components\connectAdvanced.js:222
notify @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:30
notifyNestedSubs @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:69
onStateChange @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\components\connectAdvanced.js:219
notify @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:30
notifyNestedSubs @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:69
onStateChange @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\components\connectAdvanced.js:219
dispatch @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\redux\lib\createStore.js:186
generalMiddleware @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:425
generalMiddleware @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\app.js:277
(anonymous) @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:362
refreshNotes @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:323
processTicksAndRejections @ internal/process/task_queues.js:85
async function (async)
refreshNotes @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:278
generalMiddleware @ C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:493
processTicksAndRejections @ internal/process/task_queues.js:85
Show 23 more frames
C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteText.min.js:921 webview_domReady Connect {props: {…}, context: {…}, refs: {…}, updater: {…}, version: 9, …}
C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\lib\logger.js:126 13:44:30 Starting Clipper server on port 41184

Thank you for any guidance with getting Joplin set up again!

2

I had a similar issue although with bigger files. My internet connection was pretty bad at the time, is it the same for you?
Ultimately I do not think there’s a way around that other than try on a faster network - different Wi-fi or mobile internet.
Ideally there should be a way to increase upload timeout.

3

Good to know this isn't a unique problem :slight_smile:

Though I'm not aware of connectivity issues. I keep around 1 TB of files synchronized with Amazon Cloud Drive and Arc 5 without problems. I keep a few GBs of files synchronized with Dropbox's normal folder without problems. My home Xfinity service through WiFi I've seen reach download speeds of over 10 mb/s, although I don't have any insight into the upload speeds.

Is there a way to identify the offending file so, for a temporary or imperfect solution, I can still synchronize the rest? Or is it worth uninstalling and starting from scratch again? I'm unsure if I got further this time (around 3000 items versus 800 items) because it was more-or-less random when this 16-mb file was synchronized or if there is some error that happened to pop up later and maybe my luck will be better if I start over?

4

Hmm maybe it's something else then.

5

I reinstalled after deleting the .config folder and partial Dropbox folder for a third time and it’s again hanging on the 16-mb resource.

2020-05-03 17:10:32: "Running background sync on timer..."
2020-05-03 17:10:32: "Scheduling sync operation...", "0"
2020-05-03 17:10:32: "Preparing scheduled sync"
2020-05-03 17:10:32: "Starting scheduled sync"
2020-05-03 17:10:32: "Synchronisation is already in progress. State: in_progress"
2020-05-03 17:15:20: "Uploading a large resource (resourceId: a24985258411471e87958eaab0185984, size:16412373 bytes) which may tie up the sync process."
2020-05-03 17:15:32: "Running background sync on timer..."
2020-05-03 17:15:32: "Scheduling sync operation...", "0"
2020-05-03 17:15:32: "Preparing scheduled sync"
2020-05-03 17:15:32: "Starting scheduled sync"
2020-05-03 17:15:32: "Synchronisation is already in progress. State: in_progress"
2020-05-03 17:18:44: "RevisionService::maintenance: Starting..."
2020-05-03 17:18:44: "RevisionService::maintenance: Service is enabled"
2020-05-03 17:18:44: "RevisionService::collectRevisions: Created revisions for 0 notes"
2020-05-03 17:18:44: "RevisionService::maintenance: Done in 118ms"
2020-05-03 17:20:32: "Running background sync on timer..."
2020-05-03 17:20:32: "Scheduling sync operation...", "0"
2020-05-03 17:20:32: "Preparing scheduled sync"
2020-05-03 17:20:32: "Starting scheduled sync"
2020-05-03 17:20:32: "Synchronisation is already in progress. State: in_progress"
2020-05-03 17:23:42: "FetchError: network timeout at: https://content.dropboxapi.com/2/files/upload
FetchError: network timeout at: https://content.dropboxapi.com/2/files/upload
    at C:\Users\David Cole\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\node-fetch\index.js:126:13"
2020-05-03 17:23:42: "Operations completed: "
2020-05-03 17:23:42: "updateRemote: 1"
2020-05-03 17:23:42: "createRemote: 533"
2020-05-03 17:23:42: "Total folders: 128"
2020-05-03 17:23:42: "Total notes: 2070"
2020-05-03 17:23:42: "Total resources: 6339"
2020-05-03 17:23:43: "DecryptionWorker: starting decryption..."
2020-05-03 17:23:43: "DecryptionWorker: completed decryption."
2020-05-03 17:24:08: "Scheduling sync operation...", "30000"
2020-05-03 17:24:18: "SearchEngine: Updating FTS table..."
2020-05-03 17:24:18: "SearchEngine: Updated FTS table in 41ms. Inserted: 1. Deleted: 0"
2020-05-03 17:24:38: "Preparing scheduled sync"
2020-05-03 17:24:38: "Starting scheduled sync"
2020-05-03 17:25:04: "Uploading a large resource (resourceId: a24985258411471e87958eaab0185984, size:16412373 bytes) which may tie up the sync process."
2020-05-03 17:28:42: "Running background sync on timer..."
2020-05-03 17:28:42: "Scheduling sync operation...", "0"
2020-05-03 17:28:42: "Preparing scheduled sync"
2020-05-03 17:28:42: "Starting scheduled sync"
2020-05-03 17:28:42: "Synchronisation is already in progress. State: in_progress"
2020-05-03 17:28:44: "RevisionService::maintenance: Starting..."
2020-05-03 17:28:44: "RevisionService::maintenance: Service is enabled"
2020-05-03 17:28:44: "RevisionService::collectRevisions: Created revisions for 1 notes"
2020-05-03 17:28:44: "RevisionService::maintenance: Done in 153ms"

There are larger files, I believe, but maybe something about this 16-mb file? Any ideas on how to identify this note for deletion?

Thanks!

6

However, this time, at around 800 of 8000 items, the lower-left status during syncing would not stay at “Created remote items: 1. Updated remote items: 1.” Every synchronization, it would display this message never moving beyond this item.

I recently noticed I had a similar issue, and – fingers crossed – it appears I've resolved it. Background and fix below, for anyone else that comes across this.

Tl;dr:

FetchError {name: "FetchError", message: "network timeout at:  
https://content.dropboxapi.com/2/files/upload", type: "request-timeout"
  • Yes, a file that was larger than your average JPG was blocking the sync (specifically, a 30MB pdf), and causing the above error.
  • Removing it got things flowing again.
  • There was much feasting and song.

Background:

  • sync: dropbox

Desktop:

  • Mojave 10.14.6
  • Joplin 1.7.11

Mobile:

  • iOS 14.3
  • Joplin 10.7.2
  • I first noticed a problem when I deleted a child notebook on my desktop, but the change wasn't reflected on my iPhone.
  • On my desktop I went to Help > Synchronisation status.
  • I noticed about 130 or so items did not sync (including a lot of tags, but I can't remember which item type).
  • I also noticed the notebook count for my desktop's sync status was 34/33
  • The mobile app assumed what it had received was all that existed, so it was blissfully ignorant of any issues.
  • I tried deleting the above notebook on mobile as well, but the desktop sync remained stuck on Created 1 remote item.
  • It was at about this point that I tried the below steps...

To find the offending file:

  1. In debug mode – for anyone else reading, more about debug mode here – look for this log entry:
    Uploading a large resource (resourceId: [COPY THIS ID], size:31103363 bytes) which may tie up the sync process.

  2. In Joplin: Help > Open profile directory

  3. Open: resources

  4. Search this folder with the ID you copied from the log.

Choose your own adventure:

At this point I did two things, although I'm not sure whether or not the first step is necessary for this to work. I'll leave that up to you:

  1. I deleted the note that I had attached the PDF to (via drag and drop).

    1. The problem persisted, and Joplin was still trying to upload the file.

  2. I closed Joplin.

  3. I dragged the offending file out of resources, onto my desktop.

  4. I reopened Joplin, and let it do its sync.

  5. After warning Some items cannot be synchronised, about 130 or so items that hadn't been synced were now uploading as normal.

  6. Everything now synced correctly on the iPhone app.

  7. After closing and re-opening Joplin on my desktop, the Some items cannot be synchronised error was now gone, and all was well. There was much feasting and song.

I hope this helps!