Skip to content
This repository has been archived by the owner on Jul 27, 2024. It is now read-only.

VGrive closes after awhile while syncing in the background #43

Open
dualhammers opened this issue Nov 4, 2019 · 17 comments
Open

VGrive closes after awhile while syncing in the background #43

dualhammers opened this issue Nov 4, 2019 · 17 comments
Assignees
@bcedu
Labels
bug Something isn't working

Comments

@dualhammers
Copy link

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 bcedu self-assigned this Nov 4, 2019
@bcedu bcedu added the bug Something isn't working label Nov 4, 2019
@bcedu
Copy link
Owner

bcedu commented Nov 4, 2019

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

@axel22
Copy link
Contributor

axel22 commented Nov 4, 2019

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

@dualhammers
Copy link
Author

dualhammers commented Nov 4, 2019 via email

@axel22 axel22 mentioned this issue Nov 4, 2019
Closed
@bcedu
Copy link
Owner

bcedu commented Nov 5, 2019

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
Copy link
Author

dualhammers commented Nov 5, 2019 via email

@bcedu
Copy link
Owner

bcedu commented Nov 5, 2019

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
Copy link
Author

dualhammers commented Nov 5, 2019 via email

@bcedu
Copy link
Owner

bcedu commented Nov 6, 2019

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
Copy link
Author

dualhammers commented Nov 7, 2019 via email

@tern19
Copy link

tern19 commented Nov 8, 2019 •
edited
Loading

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
Copy link
Owner

bcedu commented Nov 8, 2019

@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
Copy link

ma1onso commented Nov 13, 2019

Same error using elementary os 5.0 and VGrive 1.2.3
image

@jumpinggoofballs
Copy link

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
Copy link
Author

dualhammers commented Nov 14, 2019 via email

@MaizerGomes
Copy link

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
Copy link
Owner

bcedu commented Nov 23, 2019 •
edited
Loading

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: #53

@carlosalbaladejo
Copy link

carlosalbaladejo commented Jan 7, 2020 •
edited
Loading

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bcedu bcedu

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@axel22 @ma1onso @dualhammers @MaizerGomes @carlosalbaladejo @tern19 @bcedu @jumpinggoofballs