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 709061 - gjs consumes 100% cpu making system unresponsive
gjs consumes 100% cpu making system unresponsive
Status: RESOLVED OBSOLETE
Product: gjs
Classification: Bindings
Component: general
1.38.x
Other Linux
: Normal normal
: ---
Assigned To: gjs-maint
gjs-maint
Depends on:
Blocks:
 
 
Reported: 2013-09-30 01:18 UTC by Ankur Sinha (FranciscoD)
Modified: 2014-07-07 03:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ankur Sinha (FranciscoD) 2013-09-30 01:18:37 UTC 
Description of problem:
Sometimes after searching in the activities UI, gjs starts to index the system. This increases the hard disk usage to such an extent that my UI gets hung for a while.

Version-Release number of selected component (if applicable):
gjs-1.38.1-1.fc20.x86_64

How reproducible:
Sometimes

Steps to Reproduce:
1.Search in activities view
2.
3.

Actual results:
Sometimes gjs begins to run and causes a UI freeze due to high IO

Expected results:
gjs should run in the background and let me continue with my work

Additional info:
Similar bug on the debian tracker:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674497


Downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1013412
Comment 1 Colin Walters 2013-10-15 22:14:40 UTC 
gjs is just a library.  Maybe it's gnome-documents using tracker?  Anyways you need to figure out which application is using gjs.
Comment 2 Ankur Sinha (FranciscoD) 2013-11-04 02:33:04 UTC 
Seems like it's gnome-documents:

/usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const Main = imports.main; Main.start(); --no-default-window

Can you please confirm and reassign the bug to documents if this is correct?

Thanks,
Ankur
Comment 3 Ankur Sinha (FranciscoD) 2014-07-07 03:56:27 UTC 
Closing this. Will file a new one if the issue crops up again.