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 708178 - GMainloop time budget
GMainloop time budget
Status: RESOLVED DUPLICATE of bug 588139
Product: glib
Classification: Platform
Component: mainloop
2.37.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2013-09-16 17:47 UTC by Lionel Landwerlin
Modified: 2013-09-16 18:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gmain: add a time budget warning mechanism (9.93 KB, patch)
2013-09-16 17:48 UTC, Lionel Landwerlin
none Details | Review

Description Lionel Landwerlin 2013-09-16 17:47:14 UTC
I've been interested in looking at what blocks my mainloop, by basically saying, "This is how much time I have to run a GSource, if it goes above a given budget in milliseconds, just dump me a backtrace when the budget is elapsed.". 

Here is an implementation of that idea. I don't know if anyone is interested, but it's worth sharing. Obviously it's posix specific but the code is flagged appropriately.
Comment 1 Lionel Landwerlin 2013-09-16 17:48:54 UTC
Created attachment 255055 [details] [review]
gmain: add a time budget warning mechanism
Comment 2 Dan Winship 2013-09-16 18:08:47 UTC
there's already a bug about this... it never really got anywhere. feel free to attach your patch there and try to prod people to do something with one of the patches...

*** This bug has been marked as a duplicate of bug 588139 ***