Crashing upon song render ~90% of the time
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
### System Information
Windows 11 23H2
### LMMS Version(s)
1.3.0-alpha.1.882+db6fc29
### Most Recent Working Version
Honestly I'm unsure, probably around early 2025 if not late 2024
### Bug Summary
Whenever I goto render the track, in any project ( new and old ), LMMS just stops responding completely, the only change I see is the window title writing something like _"Rendering - 0% [Song Editor]"_
I cannot recall the version I had prior as it was a nightly, all I recall was it didn't have the SlicerT and LOMM plugin at the time.
I find the only 2 workarounds around this are:
1. Opening the project in a fresh instance ( must not have been open for too long ), and as soon as the project opens, go to render the song as quick as you can, only then will it start without issue ( closing any open windows in the project **might** help )
2. Rendering via the terminal with
```
lmms render projectfile.mmpz
```
I would use method 2 often if some of projects didn't use a VST that requires enabling every new session ( MTPDK2 )
Anyway due to this issue, I am completely unable to render my new track simply due to being too heavy, meaning it takes forever to load, thus making method 1 difficult if not impossible to execute correctly
As far as I know, I seem to be the only person experiencing this issue which is rather strange...
# EDIT (05/16/2026):
It's been... a few months.
From what I've observed
1. The crash occurs on my more heavier projects, the type that stutter during live real-time playback. They typically have a good handful of VSTs' and VSTis' loaded in.
2. The crash basically won't happen on lighter projects, best on no-VST projects.
3. On GUI render, it manages to create an 88 byte file, presumably containing header data for a `*.wav` file. But fails to write any actual audio data.
4. CLI rendering is guaranteed to work if not obvious from my initial post...
I hope that helps!
Not sure if you can consider it a "crash" in the sense it'd close itself, but it just stops responding. Maybe a thread is being hung? I'd say the UI thread but then I'd expect the audio to still continue rendering in the background isn't it...
### Expected Behaviour
The track should've began rendering without hanging the process.
### Steps To Reproduce
1. Open a project, preferably anything heavy and takes a little while to load in ( VST-heavy // heavy VSTs )
2. Goto File and Click "Export" ( alternatively, click on "Export current project" icon )
3. After setting your file name and type, click "Okay" ( or is it "Render"? )
### Logs
Click to expand
Microsoft Windows [Version 10.0.22631.5624]
(c) Microsoft Corporation. All rights reserved.C:\Users\User\Documents\mt\LMMS\Projects>lmms "I CANT SING.mmpz"
C:\Users\User\Documents\mt\LMMS\Projects>Cannot load library C:\Program Files\LMMS\plugins\carlabase.dll: The specified module could not be found.
Cannot load library C:\Program Files\LMMS\plugins\carlapatchbay.dll: The specified module could not be found.
Cannot load library C:\Program Files\LMMS\plugins\carlarack.dll: The specified module could not be found.
unique ID: SRvb
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Sanford Reverb
RemotePlugin::DebugMessage: initialization done
fluidsynth: warning: No preset found on channel 9 [bank=128 prog=0]
fluidsynth: warning: No preset found on channel 9 [bank=128 prog=0]
unique ID: PLGQ
RemotePlugin::DebugMessage: inputs: 0 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: sforzando
Unknown embed method "none"
RemotePlugin::DebugMessage: initialization done
unique ID: EMS1
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Ignite - Emissary
RemotePlugin::DebugMessage: initialization done
unique ID: NDIR
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Ignite - NadIR
RemotePlugin::DebugMessage: initialization done
unique ID: PLGQ
RemotePlugin::DebugMessage: inputs: 0 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: sforzando
Unknown embed method "none"
RemotePlugin::DebugMessage: initialization done
unique ID: EMS1
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Ignite - Emissary
RemotePlugin::DebugMessage: initialization done
unique ID: NDIR
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Ignite - NadIR
RemotePlugin::DebugMessage: initialization done
QtXmlWrapper::loadXMLfile(): empty data
unique ID: apls
RemotePlugin::DebugMessage: inputs: 0 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Ample Bass P Lite II
Unknown embed method "none"
RemotePlugin::DebugMessage: initialization done
unique ID: EMS1
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Ignite - Emissary
RemotePlugin::DebugMessage: initialization done
unique ID: NDIR
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Ignite - NadIR
RemotePlugin::DebugMessage: initialization done
unique ID: SRvb
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Sanford Reverb
RemotePlugin::DebugMessage: initialization done
unique ID: MTPD
RemotePlugin::DebugMessage: inputs: 0 output: 16
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: MT-PowerDrumKit
Unknown embed method "none"
RemotePlugin::DebugMessage: initialization done
unique ID: IVG2
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: IVGI2
RemotePlugin::DebugMessage: initialization done
unique ID: D2rt
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Dirty Filter Plus
RemotePlugin::DebugMessage: initialization done
unique ID: SRvb
RemotePlugin::DebugMessage: inputs: 2 output: 2
RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: editor successfully created
RemotePlugin::DebugMessage: plugin name: Sanford Reverb
RemotePlugin::DebugMessage: initialization done
SHGetFileInfo() timed out for C:\Users\User\Documents\mt\LMMS\Projects\I CANT SING.wavC:\Users\User\Documents\mt\LMMS\Projects>QObject::~QObject: Timers cannot be stopped from another thread
C:\Users\User\Documents\mt\LMMS\Projects>
### Screenshots / Minimum Reproducible Project
_No response_
### Please search the issue tracker for existing bug reports before submitting your own.
- [x] I have searched all existing issues and confirmed that this is not a duplicate.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the hang from the GUI Export flow with a heavy VST project, then compare it with the working `lmms render projectfile.mmpz` command. Check whether GUI rendering consistently leaves an 88-byte WAV and stops responding, while CLI rendering completes. Done means heavy projects render successfully through the GUI without hanging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100