Using the F option from Lighttable and Ctrl+Scroll to between 50 and 100 percent make Darktable crash

[KIRSJ]

Describe the bug

Darktable should not crash. I don't know what causes the crash.

Steps to reproduce

1. Select 1, 2 or n raw files from Lighttable and press F.
2. Zoom with Ctrl+Scroll-wheel.
3. At some point the crash appears.
   Sometimes the crash doesn't appear until the left- or right-keys are introduced.

Expected behavior

The crash should not happen

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

GitHub nightly

darktable version

4.9.0+892~g40f497b425

What OS are you using?

Windows

What is the version of your OS?

Microsoft Windows 11 Pro, version 10.022631

Describe your system?

Dimensioned for image editing.

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

AMD Radeon RX 6600

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

The previous nightly build brought my attention to the problem. Then I installed 4.9.0+892~g40f497b425 and the problem continued.

[pehar1]

Cannot reproduce with current master (4.9.0+901~gc098ad54da) on Ubuntu 24.04. Does this also happen disabling OpenCL ? Can you provide a -d common log ?

[KIRSJ]

Ubuntu is not the OS I reported. Yes, the problem persists with or without OpenCL.
No, Windows doesn't accept darktable.exe in the PowerShell.

[pehar1]

Troubleshooting without a log file will be difficult... , possibly impossible if nobody can reproduce.
Aren't there other command line tools in Windows like "Command Prompt", "Azure Cloud Shell", "cmd" ?
Why is PowerShell not accepting darktable.exe ? Error message ? Missing quotation marks ?

[KIRSJ]

It's crazy - now I can't reproduce the issue myself.
For my next test - how does the exact ( darktable -d common ) command syntax look?

[jenshannoschwalm]

FWIW, if you want to support the devs by providing relevant information about what happened and possibly even why, we always require a log file. Otherwise the chances for an issue getting properly fixed in short time are close to zero :-) And we know nothing about your system, all in the log file.

There is also #17684 sounding as your issue ... maybe you can discuss this with @Macchiato17 as he is also on windows and a very friendly person.

[ptilopteri]

* KIRSJ ***@***.***> [10-21-24 12:49]:

It's crazy - now I can't reproduce the issue myself. For my next test - how does the exact ( darktable -d common ) command syntax look?

right-click on the darktable.exe icon and look a properties. it will show you the executable command line. use that.

…

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

[KIRSJ]

Jens and paka, thank you both.
Of course you need documentation. I attempted to create a log when the issue stopped to manifest itself.
Maybe this report can stay open for a while, should the problem return.

[kofa73]

@KIRSJ : could it be that you had other apps open (e.g. a browser with lots of tabs), consuming lots of memory, but when you tried to reproduce the issue, that was not the case?

[KIRSJ]

kofa73,
I can't exclude such a combination. Fortunately there has been no issue for the last two weeks, and I use Darktable daily. Usually the most recent nightly build.
Should this issue reappear I'll think about your suggestion.