search

bcedu / VGrive

Google Drive client for linux
GNU General Public License v3.0
313 stars 33 forks source link

VGrive closes after awhile while syncing in the background #43

Open dualhammers opened 4 years ago

dualhammers commented 4 years ago

New install of Elementary OS (5.0, Juno) and I am trying to pull down my GDrive. Because I cannot pick certain folders I'm pulling down the entire drive (50GB). Once I started it I close the window and get told

"vGrive will continue syncing in the background"

AT first I thought it was closing when it returned to log out after a period of being idle, but it turns out it's just closing after a period of time. Because it's not finishing the sync it ends up scanning the contents it has already downloaded, which is only about 10% of the drive.

bcedu commented 4 years ago

Are you working with the lastest release of VGrive? There was a similar bug fixed in the version 1.1.0.

axel22 commented 4 years ago

I can confirm this with the release 1.2.3 (installed yesterday).

dualhammers commented 4 years ago

I am using the app center version (1.1.0)

On Mon, Nov 4, 2019 at 8:00 AM Aleksandar Prokopec notifications@github.com wrote:

I can confirm this with the release 1.2.3 (installed yesterday).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bcedu/VGrive/issues/43?email_source=notifications&email_token=ABZGBFVYTFYDSIEYVAPKKG3QSA2KHA5CNFSM4JIPA2X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC7RK7Y#issuecomment-549393791, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZGBFU22GKEHZ34FLU6RB3QSA2KHANCNFSM4JIPA2XQ .

-- Twitter | @dualhammers http://bit.ly/woDpEo

bcedu commented 4 years ago

Could you try oppenning the app from the terminal with com.github.bcedu.vgrive and let it work on background?

By oppenig throught terminal you will be able to see the last message that vgrive logs before stopping the sync process.

I've just finished a sync of 2 GB of music in the background without any problems, I'm not able to replicate the bug...

Thanks!!

dualhammers commented 4 years ago

Just did this, here's the results

For about 30 minutes it produced messages like this

` (com.github.bcedu.vgrive:25559): Json-CRITICAL **: 13:51:09.666: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:25559): Json-CRITICAL **: 13:51:09.666: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:25559): Json-CRITICAL **: 13:51:09.666: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:25559): Json-CRITICAL **: 13:51:09.666: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:25559): Json-CRITICAL **: 13:51:09.666: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:25559): Json-CRITICAL **: 13:51:09.667: json_object_get_boolean_member: assertion 'node != NULL' failed ` With the only difference being the last two digit sets in the number string (08.200, 09.200, 09.666 etc).

Then this happened.

LOG: INFO: podcasts_opml.xml not changed LOG: NEW REMOTE FILE: aud Friendendum.7z downloding... Killed

That's it.

On Tue, Nov 5, 2019 at 10:53 AM Eduard Berloso Clarà < notifications@github.com> wrote:

Could you try oppenning the app from the terminal with com.github.bcedu.vgrive and let it work on background?

By oppenig throught terminal you will be able to see the last message that vgrive logs before stopping the sync process.

I've just finished a sync of 2 GB of music in the background without any problems, I'm not able to replicate the bug...

Thanks!!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bcedu/VGrive/issues/43?email_source=notifications&email_token=ABZGBFWYOKWDPBNQBUZQG7TQSGXKBA5CNFSM4JIPA2X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDDWL6Y#issuecomment-549938683, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZGBFQYJFAXJYXEB7GAJFDQSGXKBANCNFSM4JIPA2XQ .

-- Twitter | @dualhammers http://bit.ly/woDpEo

bcedu commented 4 years ago

The "Json-CRITICAL" messages are "normal", they are controled and doesnt affect.

What it's strange is that "killed" message at the end... It looks like someone killed the process...

Was the file Friendendum. 7z very big? Could your system run out of memory? (which are your system specs?)

dualhammers commented 4 years ago

2GB File

Specs:

i7-4710HQ (2.5GHZ) 12GB Memory

System Usage without vGrive Running:

5-6% CPU usage average 2.3 GB Ram usage 93% swap file usage... 912 MiB / 976 MiB

Maybe the swap file is too small?

On Tue, Nov 5, 2019 at 2:31 PM Eduard Berloso Clarà < notifications@github.com> wrote:

The "Json-CRITICAL" messages are "normal", they are controled and doesnt affect.

What it's strange is that "killed" message at the end... It looks like someone killed the process...

Was the file Friendendum. 7z very big? Could your system run out of memory? (which are your system specs?)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bcedu/VGrive/issues/43?email_source=notifications&email_token=ABZGBFUVRPLNZOZQJJL4T3TQSHQ4FA5CNFSM4JIPA2X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDEMWKY#issuecomment-550030123, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZGBFS2NIPKEQPXLK4GSATQSHQ4FANCNFSM4JIPA2XQ .

-- Twitter | @dualhammers http://bit.ly/woDpEo

bcedu commented 4 years ago

It looks like it's more a problem of memory and not a problem caused by running on background. To confirm this theory, try running VGrive from the terminal but without sending it to background.

dualhammers commented 4 years ago

Ran it the way you suggested (via terminal without sending it to background)

Got the 'killed' command again

I ran free overnight to watch while it occured (every 5 seconds)

Here's the section of the log that looks like it was when the program killed based on the jump in ramp usage.

` total used free shared buff/cache available Mem: 11920 5259 781 49 5878 6295 Swap: 975 633 342

          total        used        free      shared  buff/cache

available Mem: 11920 5320 720 49 5878 6235 Swap: 975 633 342

          total        used        free      shared  buff/cache

available Mem: 11920 5371 669 49 5878 6183 Swap: 975 633 342

          total        used        free      shared  buff/cache

available Mem: 11920 5428 612 49 5878 6127 Swap: 975 633 342

          total        used        free      shared  buff/cache

available Mem: 11920 5497 543 49 5878 6058 Swap: 975 633 342

          total        used        free      shared  buff/cache

available Mem: 11920 5560 480 49 5878 5994 Swap: 975 633 342

          total        used        free      shared  buff/cache

available Mem: 11920 10326 1485 42 107 1366 Swap: 975 975 0

          total        used        free      shared  buff/cache

available Mem: 11920 1246 10467 41 206 10397 Swap: 975 929 46

          total        used        free      shared  buff/cache

available Mem: 11920 1247 10463 41 209 10395 Swap: 975 929 46

          total        used        free      shared  buff/cache

available Mem: 11920 1247 10460 41 212 10394 Swap: 975 929 46 `

Continues on like that (1247 used) for the rest of the night

On Wed, Nov 6, 2019 at 12:37 PM Eduard Berloso Clarà < notifications@github.com> wrote:

It looks like it's more a problem of memory and not a problem caused by running on background. To confirm this theory, try running VGrive from the terminal but without sending it to background.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bcedu/VGrive/issues/43?email_source=notifications&email_token=ABZGBFW552TRFYLTROT37X3QSMMITA5CNFSM4JIPA2X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDHXQ3I#issuecomment-550467693, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZGBFVRBXV2CKWPV56COW3QSMMITANCNFSM4JIPA2XQ .

-- Twitter | @dualhammers http://bit.ly/woDpEo

tern19 commented 4 years ago

I have the same issue. I'm running latest version of Vgrive (1.2.4-1) on Manjaro KDE ( KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 4.19.79-1-MANJARO)

Usually, Vgrive runs for about a few minutes while the application is open and then it just suddenly stops. I've tried running it via terminal and it ran for about 10 seconds. For the better part of it this is the output that I got:

(com.github.bcedu.vgrive:23527): Json-CRITICAL **: 13:06:46.145: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:23527): Json-CRITICAL **: 13:06:46.145: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:23527): Json-CRITICAL **: 13:06:46.145: json_object_get_boolean_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:23527): Json-CRITICAL **: 13:06:46.145: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:23527): Json-CRITICAL **: 13:06:46.145: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:23527): Json-CRITICAL **: 13:06:46.145: json_object_get_boolean_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:23527): Json-CRITICAL **: 13:06:46.145: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:23527): Json-CRITICAL **: 13:06:46.145: json_object_get_string_member: assertion 'node != NULL' failed

(com.github.bcedu.vgrive:23527): Json-CRITICAL **: 13:06:46.145: json_object_get_boolean_member: assertion 'node != NULL' failed
LOG: INFO: open booklet.pdf ignored
LOG: INFO: Booklet for st104.odt ignored
LOG: INFO: Booklet for st104.odt~ ignored
LOG: INFO: r-cheat-sheet-3.pdf ignored

(com.github.bcedu.vgrive:23527): GLib-GObject-CRITICAL **: 13:06:46.146: g_object_unref: assertion 'old_ref > 0' failed
LOG: INFO: clec15.pdf ignored
LOG: INFO: clec8.pdf ignored
LOG: INFO: clec18.pdf ignored
LOG: INFO: clec10.pdf ignored
LOG: INFO: clec14.pdf ignored
LOG: INFO: clec17.pdf ignored
LOG: INFO: clec19.pdf ignored
LOG: INFO: clec23.pdf ignored
LOG: INFO: clec7.pdf ignored
LOG: INFO: clec12.pdf ignored
LOG: INFO: clec13.pdf ignored
LOG: INFO: clec24.pdf ignored
LOG: INFO: clec9.pdf ignored
**

And then it finished off with this:

Gtk:ERROR:../gtk/gtk/gtktextview.c:4451:gtk_text_view_validate_onscreen: assertion failed: (priv->onscreen_validated) Bail out! Gtk:ERROR:../gtk/gtk/gtktextview.c:4451:gtk_text_view_validate_onscreen: assertion failed: (priv->onscreen_validated) LOG: INFO: clec22.pdf ignored Aborted (core dumped)

bcedu commented 4 years ago

@tern19 your error looks like a different one form the seen here. The app didnt get a 'killed' message.

Could you open a new issue with the info?

Thanks!

ma1onso commented 4 years ago

Same error using elementary os 5.0 and VGrive 1.2.3 image

jumpinggoofballs commented 4 years ago

Similar behaviour with the flatpak on Clear Linux. But different error log in the terminal:

Gtk:ERROR:gtktextview.c:4451:gtk_text_view_validate_onscreen: assertion failed: (priv->onscreen_validated) Bail out! Gtk:ERROR:gtktextview.c:4451:gtk_text_view_validate_onscreen: assertion failed: (priv->onscreen_validated)

dualhammers commented 4 years ago

We should probably split these different errors off into different issues. Multiple reasons for the same behavior means multiple issues to fix

On Thu, Nov 14, 2019, 7:52 AM jumpinggoofballs notifications@github.com wrote:

Similar behaviour with the flatpak on Clear Linux. But different error log in the terminal:

Gtk:ERROR:gtktextview.c:4451:gtk_text_view_validate_onscreen: assertion failed: (priv->onscreen_validated) Bail out! Gtk:ERROR:gtktextview.c:4451:gtk_text_view_validate_onscreen: assertion failed: (priv->onscreen_validated)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bcedu/VGrive/issues/43?email_source=notifications&email_token=ABZGBFS47QAUFABALUSQOI3QTVQ3VA5CNFSM4JIPA2X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEECC4TA#issuecomment-553922124, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZGBFXPO4N26KRJSLPATKLQTVQ3VANCNFSM4JIPA2XQ .

MaizerGomes commented 4 years ago

Same error here: Elementary OS Juno VGrive 1.3.0

** Gtk:ERROR:../../../../gtk/gtktextview.c:4442:gtk_text_view_validate_onscreen: assertion failed: (priv->onscreen_validated) [1] 5918 abort com.github.bcedu.vgrive

bcedu commented 4 years ago

Errors related with message

** Gtk:ERROR:../../../../gtk/gtktextview.c:4442:gtk_text_view_validate_onscreen: assertion failed: (priv->onscreen_validated) [1] 5918 abort com.github.bcedu.vgrive

have already been fixed here: https://github.com/bcedu/VGrive/issues/53

carlosalbaladejo commented 4 years ago

Similar error here. Elementary OS 5.1 Hera VGrive 1.3.0

From journalctl in reverse order (latest first):

ene 07 12:16:08 calbaladejo-pc kernel: com.github.bced[26960]: segfault at 24 ip 00007fda4f4d207b sp 00007fffd61ea400 error 4 in libgtk-3.so.0.2200.30[7fda4f1d0000+6f1000]
ene 07 12:16:08 calbaladejo-pc com.github.bced[26960]: Invalid text buffer iterator: either the iterator is uninitialized, or the characters/pixbufs/widgets in the buffer have been modified since the iterator was created.
                                                       You must use marks, character numbers, or line numbers to preserve a position across buffer modifications.
                                                       You can apply tags and insert marks without invalidating your iterators,
                                                       but any mutation that affects 'indexable' buffer contents (contents that can be referred to by character offset)
                                                       will invalidate all outstanding iterators
ene 07 12:16:08 calbaladejo-pc com.github.bced[26960]: file /build/com.github.bcedu.vgrive-1.3.0/src/VGriveClient.vala: line 1271: uncaught error: Setting attribute standard::type not supported (g-io-error-quark, 15)
ene 07 12:16:08 calbaladejo-pc com.github.bced[26960]: json_object_get_boolean_member: assertion 'node != NULL' failed
ene 07 12:16:08 calbaladejo-pc com.github.bced[26960]: json_object_get_string_member: assertion 'node != NULL' failed
ene 07 12:16:08 calbaladejo-pc com.github.bced[26960]: json_object_get_string_member: assertion 'node != NULL' failed
ene 07 12:16:08 calbaladejo-pc com.github.bced[26960]: json_object_get_string_member: assertion 'node != NULL' failed
ene 07 12:16:07 calbaladejo-pc com.github.bced[26960]: json_object_get_string_member: assertion 'node != NULL' failed
ene 07 12:16:07 calbaladejo-pc com.github.bced[26960]: json_object_get_string_member: assertion 'node != NULL' failed
ene 07 12:16:07 calbaladejo-pc com.github.bced[26960]: json_array_get_elements: assertion 'array != NULL' failed
ene 07 12:16:07 calbaladejo-pc com.github.bced[26960]: json_node_get_array: assertion 'JSON_NODE_IS_VALID (node)' failed

The Setting attribute standard::type not supported error had appeared before in the log without crashing the program.