racket / racket/drracket

DrRacket crashes to desktop on Windows 10 and 11 64 bit

Open
#596 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
516
Forks
103
PR merge metrics
No merged PRs in 30d

Description

Both on my physical copy with Windows 10 (latest update) and in the Virtualbox developer image of Windows 11 "WinDev2211Eval" DrRacket 8.7 crashes to desktop at unspecified times after a racket source file has been loaded. The bug might require clicking into an editor window with a source file first. The crash happens sometimes immediately, sometimes after a while (a few seconds to a few minutes). Since this might make a difference: In each test, the language was set to Custom: no debugging or profiling. The crash does not appear on my machines when no external source file is loaded.

No diagnostic messages or bug report forms appear, they are immediate crashes to desktop. DrRacket version is 8.7, downloaded from racket-lang.org and freshly installed.

To repeat: Open a source file in a fresh install of Racket. Click into the editor window a few times. Wait a few minutes, maybe click into the editor again later. It happens every time I try, although each time after a different time interval.

Workaround: The 64-bit x64 BC release works in my tests without problems.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the crash on Windows 10 or 11 using the Racket 8.7 installer, with a source file loaded in DrRacket and the language set to Custom. Compare the standard release with the 64-bit x64 BC release mentioned in the workaround; done means the reproducible crash is isolated or prevented and verified through repeated editor interaction.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.