[GH-ISSUE #8] SillyTavern Crash (Reproducible) #2

Closed
opened 2026-10-15 18:03:04 +00:00 by bsakaguchi · 3 comments
Owner

Originally created by @TheLonelyDevil9 on GitHub (Nov 26, 2025).
Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Fandom-Scraper/issues/8

Is there a limit to how many pages we can scrape via a single request?

I've had this happen thrice with ST force-closing immediately after (latest staging SillyTavern 1.14.0 'staging' (929d377da) as well as the build immediately before this one)

Image
<--- Last few GCs --->                                                                                          [29666:0xb400007360a2c000]  1090736 ms: Scavenge (interleaved) 1018.7 (1024.1) -> 1017.2 (1028.4) MB, pooled: 0 MB, 1.60 / 0.00 ms  (average mu = 0.262, current mu = 0.216) allocation failure;                                [29666:0xb400007360a2c000]  1090973 ms: Mark-Compact (reduce) 1021.1 (1028.4) -> 1017.1 (1022.1) MB, pooled: 0 MB, 196.41 / 0.00 ms  (+ 3.9 ms in 61 steps since start of marking, biggest step 0.9 ms, walltime since start of marking 207 ms) (average mu = 0                         FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory        ----- Native stack trace -----                                                                                  ./start.sh: line 16: 29666 Aborted                    node "server.js" "$@"

Technically using individual file output might solve this a s a workaround probably but it's not recommended, having a single file output would be nice I guess

Originally created by @TheLonelyDevil9 on GitHub (Nov 26, 2025). Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Fandom-Scraper/issues/8 Is there a limit to how many pages we can scrape via a single request? I've had this happen thrice with ST force-closing immediately after (latest staging SillyTavern 1.14.0 'staging' (929d377da) as well as the build immediately before this one) <img width="1440" height="2839" alt="Image" src="https://github.com/user-attachments/assets/60e5713f-63b2-4118-b0f1-bdeadd37159c" /> ``` <--- Last few GCs ---> [29666:0xb400007360a2c000] 1090736 ms: Scavenge (interleaved) 1018.7 (1024.1) -> 1017.2 (1028.4) MB, pooled: 0 MB, 1.60 / 0.00 ms (average mu = 0.262, current mu = 0.216) allocation failure; [29666:0xb400007360a2c000] 1090973 ms: Mark-Compact (reduce) 1021.1 (1028.4) -> 1017.1 (1022.1) MB, pooled: 0 MB, 196.41 / 0.00 ms (+ 3.9 ms in 61 steps since start of marking, biggest step 0.9 ms, walltime since start of marking 207 ms) (average mu = 0 FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory ----- Native stack trace ----- ./start.sh: line 16: 29666 Aborted node "server.js" "$@" ``` Technically using individual file output might solve this a s a workaround probably but it's not recommended, having a single file output would be nice I guess
Author
Owner

@Nidelon commented on GitHub (Nov 26, 2025):

https://github.com/Nidelon/SillyTavern-Fandom-Scraper
Try using my repository, I made a small fix there, and let me know if everything works stably.

UPD: Just use the latest update. The fix has already been merged into the main branch.

<!-- gh-comment-id:3580114422 --> @Nidelon commented on GitHub (Nov 26, 2025): ~~https://github.com/Nidelon/SillyTavern-Fandom-Scraper Try using my repository, I made a small fix there, and let me know if everything works stably.~~ UPD: Just use the latest update. The fix has already been merged into the main branch.
Author
Owner

@Cohee1207 commented on GitHub (Nov 26, 2025):

Worked for me at least. But I'm not using termux

<!-- gh-comment-id:3582037995 --> @Cohee1207 commented on GitHub (Nov 26, 2025): Worked for me at least. But I'm not using termux
Author
Owner

@TheLonelyDevil9 commented on GitHub (Dec 3, 2025):

UPD: Just use the latest update. The fix has already been merged into the main branch.

Thank you!

<!-- gh-comment-id:3605034129 --> @TheLonelyDevil9 commented on GitHub (Dec 3, 2025): > UPD: Just use the latest update. The fix has already been merged into the main branch. Thank you!
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
SillyTavern/SillyTavern-Fandom-Scraper#2
No description provided.