GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — startup error · Issue #1569 · processing/processing4

startup error #1569

New issue
Copy link
New issue
Copy link
Open
Open
startup error#1569
Copy link

Description

@Miuren
Miuren
opened on Sep 14, 2026
Issue body actions

After installing the new version of Processing 4-5-6 on Windows 11 pro, this screen appears

errore proc-4.pdf

I tried uninstalling and reinstalling the program but the error message keeps appearing.

what should I do?

Activity

  1. SableRaf commented on Sep 14, 2026

    @SableRaf
    SableRaf
    on Sep 14, 2026
    Collaborator
    More actions

    @Miuren The pdf link doesn't seem to work. Please edit your issue and include the image directly in the body of the issue. If possible please also describe the issue and your version of Windows.

  2. Miuren commented on Sep 14, 2026

    @Miuren
    Miuren
    on Sep 14, 2026
    Author
    More actions

    L'app parte e dopo qualche seconda appare l'errore:

    Image

    il sistema è windows 11 pro
    processore AMD Ryzen 9 6900 HX
    Build di Windows: 26200
    Processori: 16
    Velocità processore: 3294 MHz
    Memoria: 32035 MB
    Piattaforma: 64 Bit

    errore proc-4.pdf

  3. tychedelia
    added a commit that references this issue on Sep 14, 2026

    Fix: only pass --disable-awt for WebGPU renderer

    76feca7
  4. Miuren commented on Sep 15, 2026

    @Miuren
    Miuren
    on Sep 15, 2026
    Author
    More actions

    Solved.
    I opened preference.txt with a text editor, searched for strings starting with instance_server.port= (and, if present, instance_server.key=), and deleted them.
    After restarting the app, the error disappeared and it works properly.
    Thanks for your support.

  5. SableRaf commented on Sep 15, 2026

    @SableRaf
    SableRaf
    on Sep 15, 2026
    Collaborator
    More actions

    Thanks for following up @Miuren do you happen to have a copy of the old preference.txt? It could help maintainers diagnose the issue and make a more robust fix.

  6. Miuren commented on Sep 15, 2026

    @Miuren
    Miuren
    on Sep 15, 2026 via email
    Author
    More actions
    Non ho fatto una copia del file prima di modificarlo. L'intervento che ho fatto è stato quello di cancellare le due righe che contenevano : instance_server.key instance_server.port riavviata l'App le due righe si sono ricreate ed adesso contengono: instance_server.key=0.5487005828390797 instance_server.port=55187 La soluzione che ho utilizzato è stata proposta da Claude a cui avevo fatto la seguente domanda: *After installing the new version of Processing 4-5-6 on Windows 11 pro, this screen appears (see image)* *I tried uninstalling and reinstalling the program but the error message keeps appearing.what should I do?* La risposta di Claude è stata: È un bug noto di Processing: il file preferences.txt contiene un valore corrotto per instance_server.port (spesso causato da firewall/antivirus/proxy che blocca la connessione che Processing usa per verificare se è già in esecuzione). Disinstallare e reinstallare non risolve nulla perché quel file *non viene toccato* dall'installer/uninstaller. Ecco come risolvere: 1. Chiudi ProcessingAssicurati che Processing non sia in esecuzione (controlla anche il Task Manager, potrebbe essere rimasto un processo appeso). 2. Apri la cartella delle preferenzeApri Esplora File e incolla nella barra degli indirizzi: %APPDATA%\Processing — premi Invio. Questa è la cartella (C:\Users\<tuo utente>\AppData\Roaming\Processing) dove si trova preferences.txt. 3. Apri preferences.txt con il Blocco NoteFai clic destro sul file preferences.txt e aprilo con Blocco Note (o un editor di testo qualsiasi). 4. Trova ed elimina la riga incriminataCerca la riga che inizia con instance_server.port= (e se presente anche instance_server.key=). Elimina quella/quelle riga/righe per intero, poi salva il file. 5. Riavvia ProcessingApri Processing normalmente: all'avvio rigenererà automaticamente quei valori in modo corretto e l'errore dovrebbe sparire. ho effettuato i cambiamenti sul file e Processing si è avviato in maniera corretta. Cordiali slauti. Mauro Bosio Il giorno mar 15 set 2026 alle ore 16:51 Raphaël de Courville < ***@***.***> ha scritto:
    …
    *SableRaf* left a comment (processing/processing4#1569) <#1569 (comment)> The hanks for following up @Miuren <https://github.com/Miuren> do you happen to have a copy of the old preference.txt? It could help maintainers diagnose the issue and make a more robust fix. — Reply to this email directly, view it on GitHub <#1569?email_source=notifications&email_token=A6D4BL2SCZZHRFVMSGCSZJD5PFJORA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNRYGIZTSMRXGMZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5682392733>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6D4BL5TUZ7DHTT652RZLG35PFJORAVCNFSNUABFKJSXA33TNF2G64TZHM4DINBTHAZDONRZHNEXG43VMU5TKNBUHA4TOMRXHAZKC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/A6D4BL2WVRZ7GLJS43CIO7L5PFJORA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNRYGIZTSMRXGMZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/A6D4BL5FRZYP27JHVMMD6RL5PFJORA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNRYGIZTSMRXGMZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>
  7. catilac commented on Sep 16, 2026

    @catilac
    catilac
    on Sep 16, 2026
    Collaborator
    More actions

    @Miuren this should be fixed in the upcoming release candidate, would you be able to try this? https://github.com/processing/processing4/releases/tag/processing-1435-4.5.7-rc

  8. catilac
    closed this as completedon Sep 16, 2026
  9. catilac
    reopened this on Sep 16, 2026
  10. catilac commented on Sep 16, 2026

    @catilac
    catilac
    on Sep 16, 2026
    Collaborator
    More actions

    this should be fixed by #1570

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.