After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 752063 - Account creation is freezing with no error or possible cancellation
Account creation is freezing with no error or possible cancellation
Status: RESOLVED INCOMPLETE
Product: geary
Classification: Other
Component: accounts
0.10.x
Other Linux
: Normal critical
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-07-07 12:06 UTC by Michael Mercier
Modified: 2016-06-05 09:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
qtdemux: rework segment event pushing (8.46 KB, patch)
2016-04-26 21:53 UTC, Thiago Sousa Santos 		rejected Details | Review
qtdemux: offset edts segments by the min timestamp of the stream (2.01 KB, patch)
2016-04-26 21:54 UTC, Thiago Sousa Santos 		rejected Details | Review

Description Michael Mercier 2015-07-07 12:06:16 UTC 
When, I try to create an account (even a fake one) the account wizard is stuck on "Please wait while Greary validates your account" and after some time it freeze using 100% of one CPU. 

There is no way to cancel or see what is happening no message even in debug mode.

I'm using Geary 0.10.0 on Archlinux.

Thanks

MM
Comment 1 Robert Schroll 2015-07-07 14:45:16 UTC 
You could try running geary under gdb, breaking during the freeze, and getting a stack trace.  If you resume and break again several times, you can see if it's stuck at a particular place or in some kind of loop.
Comment 2 Michael Gratton 2016-03-26 03:03:05 UTC 
Hi Michael, thanks for reporting the problem.

Is it still an issue for you? If so, can you obtain a backtrace of the crash and attach it to this bug? Follow the steps to produce the file geary.gdb as outlined here: https://wiki.gnome.org/Apps/Geary/FAQ then attach it to this bug.
Comment 3 Thiago Sousa Santos 2016-04-26 21:53:57 UTC 
Created attachment 326806 [details] [review]
qtdemux: rework segment event pushing

Instead of always keeping a safe segment (start=0) event from the beginning,
delay the creation of this event to when we really know the timestamp of the
first sample. This is important to properly start fragmented streams that
we might join in the middle or to play isolated fragment files that might
have an advanced tfdt.
Comment 4 Thiago Sousa Santos 2016-04-26 21:54:03 UTC 
Created attachment 326807 [details] [review]
qtdemux: offset edts segments by the min timestamp of the stream

Otherwise if the stream is starting at timestamp=X it would wait
'X' to start playing.
Comment 5 Michael Gratton 2016-04-27 01:21:29 UTC 
(In reply to Thiago Sousa Santos from comment #4)
> Created attachment 326807 [details] [review] [review]
> qtdemux: offset edts segments by the min timestamp of the stream
> 
> Otherwise if the stream is starting at timestamp=X it would wait
> 'X' to start playing.

Thiago, I think you attached this to the wrong bug.
Comment 6 Thiago Sousa Santos 2016-04-27 01:28:27 UTC 
Sorry, indeed wrong bug.
Comment 7 Michael Gratton 2016-06-05 09:19:50 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.

Thanks!