Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4341] [BUG]: font issue prevents upload/parsing of PDF #2766

New Issue
Closed
opened 2026-02-22 18:31:09 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:31:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @socketbox on GitHub (Aug 29, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4341

Originally assigned to: @shatfield4 on GitHub.

How are you running AnythingLLM?

Docker (local)

What happened?

I attempt to upload a document and receive the following:

[2025-08-29 21:55:35]» ./start_docker.sh
[collector] info: [TikTokenTokenizer] Initialized new TikTokenTokenizer instance.
[collector] info: Collector hot directory and tmp storage wiped!
[collector] info: Document processor app listening on port 8888
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma

✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 377ms

Start using Prisma Client in Node.js (See: https://pris.ly/d/client)

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate)

import { PrismaClient } from '@prisma/client/edge'
const prisma = new PrismaClient()


See other ways of importing Prisma Client: http://pris.ly/d/importing-client

npm notice
npm notice New major version of npm available! 10.8.2 -> 11.5.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.5.2
npm notice To update run: npm install -g npm@11.5.2
npm notice
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db"

33 migrations found in prisma/migrations


No pending migrations to apply.
┌─────────────────────────────────────────────────────────┐
│  Update available 5.3.1 -> 6.15.0                       │
│                                                         │
│  This is a major update - please follow the guide at    │
│  https://pris.ly/d/major-version-upgrade                │
│                                                         │
│  Run the following to update                            │
│    npm i --save-dev prisma@latest                       │
│    npm i @prisma/client@latest                          │
└─────────────────────────────────────────────────────────┘
[backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data.
[backend] info: [TokenManager] Initialized new TokenManager instance for model: gpt-3.5-turbo
[backend] info: [TokenManager] Returning existing instance for model: gpt-3.5-turbo
[backend] info: [SSL BOOT ENABLED] Loading the certificate and key for HTTPS mode...
[backend] info: [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM.
[backend] info: prisma:info Starting a sqlite pool with 17 connections.
[backend] info: [TELEMETRY SENT] {"event":"server_boot","distinctId":"1929a828-11ed-4826-a265-68ebef1285d3","properties":{"commit":"--","runtime":"docker"}}
[backend] info: [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services.
[backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data.
[backend] info: Primary server in HTTPS mode listening on port 33001
[backend] info: [BackgroundWorkerService] Starting...
[backend] info: [BackgroundWorkerService] Service started with 1 jobs ["cleanup-orphan-documents"]
[backend] info: [MetaGenerator] fetching custom meta tag settings...
prisma:info Starting a sqlite pool with 17 connections.
[backend] info: [131:260]: No direct uploads path found - exiting.
[bg-worker][cleanup-orphan-documents] info: [131:260]: No direct uploads path found - exiting.
[backend] warn: Child process exited with code 0 and signal null
[backend] info: Worker for job "cleanup-orphan-documents" exited with code 0
[backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data.
[collector] info: -- Working NFPA-70_NEC2020.pdf --
^C[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
[collector] info: Warning: Ran out of space in font private use area.
...

Are there known steps to reproduce?

I'd attach the file in question but it's over 100MB.

A similar issue was reported in #3739

Originally created by @socketbox on GitHub (Aug 29, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4341 Originally assigned to: @shatfield4 on GitHub. ### How are you running AnythingLLM? Docker (local) ### What happened? I attempt to upload a document and receive the following: ``` [2025-08-29 21:55:35]» ./start_docker.sh [collector] info: [TikTokenTokenizer] Initialized new TikTokenTokenizer instance. [collector] info: Collector hot directory and tmp storage wiped! [collector] info: Document processor app listening on port 8888 Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma ✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 377ms Start using Prisma Client in Node.js (See: https://pris.ly/d/client) import { PrismaClient } from '@prisma/client' const prisma = new PrismaClient() or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate) import { PrismaClient } from '@prisma/client/edge' const prisma = new PrismaClient() See other ways of importing Prisma Client: http://pris.ly/d/importing-client npm notice npm notice New major version of npm available! 10.8.2 -> 11.5.2 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.5.2 npm notice To update run: npm install -g npm@11.5.2 npm notice Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db" 33 migrations found in prisma/migrations No pending migrations to apply. ┌─────────────────────────────────────────────────────────┐ │ Update available 5.3.1 -> 6.15.0 │ │ │ │ This is a major update - please follow the guide at │ │ https://pris.ly/d/major-version-upgrade │ │ │ │ Run the following to update │ │ npm i --save-dev prisma@latest │ │ npm i @prisma/client@latest │ └─────────────────────────────────────────────────────────┘ [backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data. [backend] info: [TokenManager] Initialized new TokenManager instance for model: gpt-3.5-turbo [backend] info: [TokenManager] Returning existing instance for model: gpt-3.5-turbo [backend] info: [SSL BOOT ENABLED] Loading the certificate and key for HTTPS mode... [backend] info: [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM. [backend] info: prisma:info Starting a sqlite pool with 17 connections. [backend] info: [TELEMETRY SENT] {"event":"server_boot","distinctId":"1929a828-11ed-4826-a265-68ebef1285d3","properties":{"commit":"--","runtime":"docker"}} [backend] info: [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services. [backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data. [backend] info: Primary server in HTTPS mode listening on port 33001 [backend] info: [BackgroundWorkerService] Starting... [backend] info: [BackgroundWorkerService] Service started with 1 jobs ["cleanup-orphan-documents"] [backend] info: [MetaGenerator] fetching custom meta tag settings... prisma:info Starting a sqlite pool with 17 connections. [backend] info: [131:260]: No direct uploads path found - exiting. [bg-worker][cleanup-orphan-documents] info: [131:260]: No direct uploads path found - exiting. [backend] warn: Child process exited with code 0 and signal null [backend] info: Worker for job "cleanup-orphan-documents" exited with code 0 [backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data. [collector] info: -- Working NFPA-70_NEC2020.pdf -- ^C[collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. [collector] info: Warning: Ran out of space in font private use area. ... ``` ### Are there known steps to reproduce? I'd attach the file in question but it's over 100MB. A similar issue was reported in #3739
yindo added the possible buginvestigating labels 2026-02-22 18:31:09 -05:00
yindo closed this issue 2026-02-22 18:31:09 -05:00
yindo commented 2026-02-22 18:31:09 -05:00
Author
Owner
Copy Link
Copy Source

@socketbox commented on GitHub (Aug 31, 2025):

Upon inspecting the document's properties, I see that all fonts in the document are listed as embedded, CID fonts.

@socketbox commented on GitHub (Aug 31, 2025): Upon inspecting the document's properties, I see that all fonts in the document are listed as embedded, CID fonts.
yindo commented 2026-02-22 18:31:09 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Sep 3, 2025):

Possible example: https://github.com/mozilla/pdf.js/issues/9279#issuecomment-351966756

@timothycarambat commented on GitHub (Sep 3, 2025): Possible example: https://github.com/mozilla/pdf.js/issues/9279#issuecomment-351966756
yindo commented 2026-02-22 18:31:09 -05:00
Author
Owner
Copy Link
Copy Source

@shatfield4 commented on GitHub (Dec 22, 2025):

@socketbox when you upload your file where it gets these errors, are they just warnings or does the file actually fail to upload and parse?

Going to close this for now since on my end with a test file, I am able to see console warnings but the file does upload and parse the content correctly. If the file does cause the collector to crash or fails to upload all together, please provide as much info as you can about this so we can replicate the problem.

@shatfield4 commented on GitHub (Dec 22, 2025): @socketbox when you upload your file where it gets these errors, are they just warnings or does the file actually fail to upload and parse? Going to close this for now since on my end with a test file, I am able to see console warnings but the file does upload and parse the content correctly. If the file does cause the collector to crash or fails to upload all together, please provide as much info as you can about this so we can replicate the problem.
yindo changed title from [BUG]: font issue prevents upload/parsing of PDF to [GH-ISSUE #4341] [BUG]: font issue prevents upload/parsing of PDF 2026-06-05 14:48:26 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label investigating possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2766
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?