'
> lib/validators/post_validator.rb:80:in `max_mention_validator'
> lib/validators/post_validator.rb:17:in `validate'
> lib/post_revisor.rb:499:in `update_post'
> lib/post_revisor.rb:460:in `revise'
> lib/post_revisor.rb:454:in `revise_and_create_new_version'
> lib/post_revisor.rb:357:in `revise_post'
> lib/post_revisor.rb:279:in `block in revise!'
> lib/post_revisor.rb:278:in `revise!'
> app/controllers/posts_controller.rb:276:in `update'
> app/controllers/application_controller.rb:427:in `block in with_resolved_locale'
> app/controllers/application_controller.rb:427:in `with_resolved_locale'
> lib/middleware/omniauth_bypass_middleware.rb:64:in `call'
> lib/content_security_policy/middleware.rb:12:in `call'
> lib/middleware/anonymous_cache.rb:403:in `call'
> lib/middleware/csp_script_nonce_injector.rb:12:in `call'
> config/initializers/008-rack-cors.rb:14:in `call'
> config/initializers/100-quiet_logger.rb:20:in `call'
> config/initializers/100-silence_logger.rb:29:in `call'
> lib/middleware/enforce_hostname.rb:24:in `call'
> lib/middleware/processing_request.rb:12:in `call'
> lib/middleware/request_tracker.rb:385:in `call'
>
> ```
These may be related [with this](https://meta.discourse.org/t/errors-in-logs-since-the-latest-update/322209), but in my case they seem to persist. And, as [mentioned there](https://meta.discourse.org/t/errors-in-logs-since-the-latest-update/322209/3), the logs do seem to get truncated sometimes.
And what all this looks like in /logs:
Any clues on what might be causing these? Can I prove any other info?
---
### Author:  [@Indra](https://meta.discourse.org/u/Indra)
#### Post date: [March 20, 2025, 8:15pm UTC](https://meta.discourse.org/t/workers-miniracer-scriptterminatederror-timeouts-in-logs/356239/3 "2025-03-20T20:15:57Z")
> [@mentalstring](#):
>
> MiniRacer::ScriptTerminatedError (terminated) lib/pretty\_text.rb:239:in `eval' lib/pretty_text.rb:239:in `block in markdown’ lib/pretty\_text.rb:691:in `block in protect' lib/pretty_text.rb:691:in `syn
Seeing this same error on our instance when posting/editing/approving a topic with very specific Markdown content. It will load for a while and then throw internal server error.
---
### Author:  [@mentalstring](https://meta.discourse.org/u/mentalstring)
#### Post date: [March 20, 2025, 8:34pm UTC](https://meta.discourse.org/t/workers-miniracer-scriptterminatederror-timeouts-in-logs/356239/4 "2025-03-20T20:34:39Z")
FWIW, we have also seen sporadic reports from users with similar errors when editing some posts (usually quite long, although not close to the limit), where making tiny changes to the text seem to overcome the error (anecdotally: adding another period, replacing a dash, etc). Haven’t been able to find reproducible steps yet as I usually hear about it only when someone found the “magic trick” to it.
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [April 3, 2025, 9:36am UTC](https://meta.discourse.org/t/workers-miniracer-scriptterminatederror-timeouts-in-logs/356239/5 "2025-04-03T09:36:47Z")
I’ve just noticed these warnings as well. When they start, they may have several recurrences within an hour or so, then stop. Until next time. I’d swear we didn’t have them until a few days ago.
---
### Author:  [@mentalstring](https://meta.discourse.org/u/mentalstring)
#### Post date: [April 3, 2025, 1:30pm UTC](https://meta.discourse.org/t/workers-miniracer-scriptterminatederror-timeouts-in-logs/356239/6 "2025-04-03T13:30:00Z")
Which version are you on, @icaria36 and @Indra? We are on `stable`, but I’m wondering if this is also happening in `tests-passed`.
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [April 3, 2025, 3:25pm UTC](https://meta.discourse.org/t/workers-miniracer-scriptterminatederror-timeouts-in-logs/356239/7 "2025-04-03T15:25:16Z")
We are on 3.5.0.beta3-dev ([3f353a726b](https://github.com/discourse/discourse/commits/3f353a726bdb20ffce08f2641cc9ff3754aed1a7)).
---
### Author:  [@mentalstring](https://meta.discourse.org/u/mentalstring)
#### Post date: [April 3, 2025, 6:38pm UTC](https://meta.discourse.org/t/workers-miniracer-scriptterminatederror-timeouts-in-logs/356239/8 "2025-04-03T18:38:02Z")
I think have found something likely related to this and that may provide some more clues to the source of the problem. This gets a bit long-winded, so please bear with me.
I noticed today that I have a couple sidekiq jobs that fail and have been retrying for at least a week with the same error as in the `/logs`.
On the console, if I retry to rebake that specific post, it takes a long time (near 30s) and eventually ends in
> **error**
>
> ```plaintext
> lib/pretty_text.rb:239:in `eval': terminated (MiniRacer::ScriptTerminatedError)
> from lib/pretty_text.rb:239:in `block in markdown'
> from lib/pretty_text.rb:691:in `block in protect'
> from lib/pretty_text.rb:691:in `synchronize'
> from lib/pretty_text.rb:691:in `protect'
> from lib/pretty_text.rb:176:in `markdown'
> from lib/pretty_text.rb:302:in `cook'
> from app/models/post_analyzer.rb:30:in `cook'
> from app/models/post.rb:357:in `cook'
> from app/models/post.rb:825:in `rebake!'
> from (discourse):1:in `'
>
> ```
After some experimenting, it seems it is due to a particular upload reference that is being used multiple times (25+) in the same post:
The time for the post to rebake is proportional to the number of times that image is referenced in it (1-2 seconds per each use). If it is mentioned enough times, it eventually hits the timeout error. However, if another uploaded image is mentioned as many or more times, the rebake is always instant.
Saving the same image and uploading it again doesn’t reproduce the problem. So the issue seems to be with a particular upload reference.
If all this is not odd enough, it gets stranger. Noticing that the re-uploaded image was including the file extension in the upload reference, I tried appending `.gif` to the problematic upload reference and… then the rebake works instantly as it should – even when the same problematic image is used dozens of times. In other words, I changed something like
``
to
``
and, somehow, that made this weird timeout error to go away.
Guess: some reprocessing needs to be done to this image  and for some reason it repeatedly fails, extending the baking process long enough for it to eventually fail? I’m not sure how to go from here.
In any case, this seems like a bug that could use some attention – maybe the [@moderators](https://meta.discourse.org/groups/moderators) can relocate this to #Contribute > Bug if they agree?