Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking down errors #537

Closed
jncsotk30 opened this issue Aug 10, 2024 · 0 comments
Closed

Tracking down errors #537

jncsotk30 opened this issue Aug 10, 2024 · 0 comments

Comments

@jncsotk30
Copy link

jncsotk30 commented Aug 10, 2024

Hello All.

I'm not the most familiar with GJS, but how are we supposed to track down the source file for which an error originates assuming it started after modifying one of my own custom widgets? I don't recall which file it was and now have no idea where to go to resolve whatever is triggering the following...

(com.github.Aylur.ags:140015): Gjs-Console-WARNING **: 13:09:30.535: Error: expected Pixbuf or string for icon, but got boolean set icon@resource:///com/github/Aylur/ags/widgets/icon.js:53:26 bind/callback<@resource:///com/github/Aylur/ags/widgets/widget.js:53:30 hook/<@resource:///com/github/Aylur/ags/widgets/widget.js:43:25 _init/GLib.MainLoop.prototype.runAsync/</<@resource:///org/gnome/gjs/modules/core/overrides/GLib.js:266:34

(com.github.Aylur.ags:141835): Gjs-CRITICAL **: 13:14:17.879: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. The offending signal was destroy on Ags_Label 0x55e9c0224050. == Stack trace for context 0x55e9bfafd210 == #0 55e9bfbc9058 i resource:///org/gnome/gjs/modules/core/overrides/GLib.js:266 (28f2f1f7d560 @ 139)

@Aylur Aylur mentioned this issue Sep 25, 2024
Merged
@Aylur Aylur closed this as not planned Won't fix, can't repro, duplicate, stale Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants