QPQ-AG/GajuDesk
10
0
Fork 0
Code Issues 8 Pull Requests Actions Packages Projects Releases Wiki Activity

Misbehaving server can crash GajuDesk #25

New Issue
Closed
opened 2025-08-14 14:47:31 +09:00 by spivee · 1 comment
spivee commented 2025-08-14 14:47:31 +09:00
Member
Copy Link
Copy Source

A user was leaving GajuMine open overnight with an attached GajuDesk window, which gives us a window into what leaving GajuDesk open for a long time does. It turns out what it does is it notices every time we screw things up in the public nodes, and crashes... At least, that is what I would guess, looking at the logs. There's various failed requests, and then eventually the check_balance call specifically starts failing in a way that triggers the supervisor tree. The GajuMine detail is its own issue, issue #10 to be exact, but the underlying crash is probably worth looking at all on its own, one day.

A user was leaving GajuMine open overnight with an attached GajuDesk window, which gives us a window into what leaving GajuDesk open for a long time does. It turns out what it does is it notices every time we screw things up in the public nodes, and crashes... At least, that is what I would guess, looking at the logs. There's various failed requests, and then eventually the check_balance call specifically starts failing in a way that triggers the supervisor tree. The GajuMine detail is its own issue, issue #10 to be exact, but the underlying crash is probably worth looking at all on its own, one day.
20250804_133757.qpq-gajumine.log
41 KiB
zxq9 added the bug label 2025-10-17 17:58:54 +09:00
zxq9 commented 2026-05-10 15:37:50 +09:00
Owner
Copy Link
Copy Source

This seems related to the problem that previous versions of GajuMine were opening GajuDesk within the same runtime context, and a problem with one became a problem with the other. There were other issues with that approach as well, but this was a lingering one.

This seems related to the problem that previous versions of GajuMine were opening GajuDesk within the same runtime context, and a problem with one became a problem with the other. There were other issues with that approach as well, but this was a lingering one.
zxq9 closed this issue 2026-05-10 15:37:50 +09:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 pig lipstick
Muggle-facing enhancements
 question
More information is needed
 wontfix
This won't be fixed
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Dagadunn Pickmick dimitar.p.ivanov flambard (Markus Flambard) gchewy hans_sv pharpend spivee (Jarvis Carroll) thescientress (Cecille de Jesus) uwiger (Ulf Wiger) zxq9 (Craig Everett)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QPQ-AG/GajuDesk#25
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?