Skip to main content
BigEricUSA
Inspiring
September 30, 2026
Answered

Newb: ON1 Effects 2025 crash

  • September 30, 2026
  • 9 replies
  • 46 views

I’m hoping someone here can shed some light on this…

My environment: Mac Mini M4 Pro, 48GB RAM. OS Sequoia. Photoshop 2026 fresh install.

I’m trying to install ON1 Effects 2025 but when I invoke it from the filter menu the ON1 environment launches only partially, mostly shades of dark grey. Then a progress window briefly shows up, above it it says “Downloading assets” and below it it says it’s updating something I think. Then the whole ON1 window crashes. PS seems unaffected.

The ON1 log says:

2026-09-26 18:48:05 ON1 - PANIC: ONCoreStackNode::removeNode("bundle_details")
2026-09-26 18:48:05 ON1 - 
********** Begin Stack Dump - bundle_details
0   ONCore17                            0x000000010a0c0750 ONProcessDumpStack + 60
1   ONQtCore                            0x000000010e5fb880 _ZN15ONCoreStackNode10removeNodeEPS_ + 208
2   ONQtCore                            0x000000010e61c294 _ZN16ONCoreStackGroup10removeNodeEP15ONCoreStackNode + 84
3   ONQtCore                            0x000000010e6a5808 _ZN15PCStackDocCtrlr33removeUnsupportedBundlesFromGroupEP16ONCoreStackGroup + 240
4   ONQtCore                            0x000000010e6a55ac _ZN15PCStackDocCtrlr24removeUnsupportedBundlesEP12PCStackCtrlr + 32
5   ONQtCore                            0x000000010e6a5980 _ZN15PCStackDocCtrlr15migrateSettingsEP12PCStackCtrlr + 168
6   ONQtCore                            0x000000010e6a62b8 _ZN15PCStackDocCtrlr8addLayerERK7QStringP12PCStackCtrlr + 88
7   ONQtCore                            0x000000010e6a66fc _ZN15PCStackDocCtrlr16loadArchivePartsEPK8__CFData18PCStackArchivePart + 780
8   ON1 Effects                         0x0000000103021a70 _ZN17PLPresetProcessor14createDocCtrlrEP15ONNDApplyParams7_ONRectRP15PCStackDocCtrlrRb + 184
9   ON1 Effects                         0x0000000103021d80 _ZN17PLPresetProcessor22createRenderImageImageEP15ONNDApplyParamsRP11ONCoreImageRb + 192
10  ON1 Effects                         0x0000000103022760 _ZN17PLPresetProcessor17createRenderImageEP15ONNDApplyParamsRP11ONCoreImageRb + 200
11  ON1 Effects                         0x0000000103022d9c _ZN17PLPresetProcessor9applyImplEP15ONNDApplyParamsRP9__ONImage + 208
12  ON1 Effects                         0x000000010302304c _ZN17PLPresetProcessor5applyEP15ONNDApplyParamsRP9__ONImage + 12
13  ONQtCore                            0x000000010e541fb0 _ZN11ONNDService9applySyncEP15ONNDApplyParamsRP9__ONImage + 124
14  ONQtCore                            0x000000010e52fa9c _ZN20ONPreviewSvcRunnable11applyPresetERP7__ONDocRK7_ONRect + 932
15  ONQtCore                            0x000000010e52ad8c _ZN20ONPreviewSvcRunnable4loadEv + 1136
********** End Stack Dump

2026-09-26 18:48:15 ON1* - QOpenGLContext::makeCurrent() called with non-opengl surface 0x60000347c790
2026-09-26 18:48:15 ON1* - QRhiGles2: Failed to make context current. Expect bad things to happen.
2026-09-26 18:48:15 ON1* - QOpenGLContext::makeCurrent() called with non-opengl surface 0x60000347c790
2026-09-26 18:48:15 ON1* - QRhiGles2: Failed to make context current. Expect bad things to happen.
2026-09-26 18:48:15 ON1* - QOpenGLContext::makeCurrent() called with non-opengl surface 0x60000347c790
2026-09-26 18:48:15 ON1* - QRhiGles2: Failed to make context current. Expect bad things to happen.
2026-09-26 18:48:15 ON1* - QOpenGLContext::makeCurrent() called with non-opengl surface 0x60000347c790
2026-09-26 18:48:15 ON1* - QRhiGles2: Failed to make context current. Expect bad things to happen.
2026-09-26 18:48:15 ON1* - QOpenGLContext::makeCurrent() called with non-opengl surface 0x60000347c790
2026-09-26 18:48:15 ON1* - QRhiGles2: Failed to make context current. Expect bad things to happen.
2026-09-26 18:48:15 ON1* - QOpenGLContext::makeCurrent() called with non-opengl surface 0x60000347c790
2026-09-26 18:48:15 ON1* - QRhiGles2: Failed to make context current. Expect bad things to happen.
2026-09-26 18:48:16 ON1* - QOpenGLContext::makeCurrent() called with non-opengl surface 0x60000347c790
2026-09-26 18:48:16 ON1* - QRhiGles2: Failed to make context current. Expect bad things to happen.
2026-09-26 18:48:16 ON1* - QOpenGLContext::makeCurrent() called with non-opengl surface 0x60000347c790
2026-09-26 18:48:16 ON1* - QRhiGles2: Failed to make context current. Expect bad things to happen.
2026-09-26 18:48:20 ON1* - QOpenGLContext::makeCurrent() called with non-opengl surface 0x60000347c790
2026-09-26 18:48:20 ON1* - QRhiGles2: Failed to make context current. Expect bad things to happen.

I’ve tried turning off “Use graphics processor” in PS. ON1 still crashes.

Can anyone think of a solution?

ON1 Effects runs as expected in “Standalone” mode, weirdly. It’s when invoked from PS that it crashes.

Correct answer Jeff Arola

I tested ON1 Effects 2025 on a variety of Macs and unfortunately the results were not good.

 

  1. Tried macOS Sequoia 15.8.1 (Intel and Apple Silicon), Tahoe 26.7.1 and Golden Gate 27.0.1 on Apple Silicon and none would run the Effects 2025 plugin from Photoshop versions 2021 thru 2026.
  2. The one macOS it did work on was macOS Monterey 12.7.6 on a 2013 Mac Pro with Photoshop 2024.

 

I heard back from ON1 support and their explanation was that the recent security updates to the last several macOS systems are the cause.

Very unlikely ON1 will fix the issue since a newer 2026 Effects version is out.

 

The 2026 Effects version does seem to work on Sequoia, Tahoe and Golden Gate.

 

9 replies

Jeff Arola
Community Expert
Jeff ArolaCommunity ExpertCorrect answer
Community Expert
October 1, 2026

I tested ON1 Effects 2025 on a variety of Macs and unfortunately the results were not good.

 

  1. Tried macOS Sequoia 15.8.1 (Intel and Apple Silicon), Tahoe 26.7.1 and Golden Gate 27.0.1 on Apple Silicon and none would run the Effects 2025 plugin from Photoshop versions 2021 thru 2026.
  2. The one macOS it did work on was macOS Monterey 12.7.6 on a 2013 Mac Pro with Photoshop 2024.

 

I heard back from ON1 support and their explanation was that the recent security updates to the last several macOS systems are the cause.

Very unlikely ON1 will fix the issue since a newer 2026 Effects version is out.

 

The 2026 Effects version does seem to work on Sequoia, Tahoe and Golden Gate.

 

BigEricUSAAuthor
Inspiring
October 2, 2026

Thank you so much :-) Where did you find that info? You’d think they would flag that prominently in the installer somewhere...

BigEricUSAAuthor
Inspiring
October 2, 2026

…Did you test this for yourself…?

jane-e
Community Expert
jane-eCommunity Expert
Community Expert
October 1, 2026

​@BigEricUSA 

What did ON1 say when you submitted a request to them? https://on1help.zendesk.com/hc/en-us

Jane

BigEricUSAAuthor
Inspiring
October 2, 2026

Having read the section in their FAQs that said “How do I know if my issue has been fixed? ~ The release notes in the next release will list issues that have been fixed”, I didn’t bother. There’s a new version out. :-)

creative explorer
Community Expert
creative explorerCommunity Expert
Community Expert
October 1, 2026

​@BigEricUSA I wonder if it ON1 Effects may not work on your MAC M series. You could try to see if Open using Rosetta. Quit both Adobe Photoshop 2026 and ON1 Effects. Go and navigate to Applications > Adobe Photoshop 2026. Right-click or Get Info (or press Cmd I). In the Info window, check the box for Open using Rosetta. Launch Photoshop and test Filter > ON1 > ON1 Effects 2025.

 

m
BigEricUSAAuthor
Inspiring
October 1, 2026

Thanks for responding :-) I’ve tried Rosetta to no avail. The weird thing is that the app works as expected in Standalone mode. It’s only when used as a plugin that it crashes.

Barry Rudick
Inspiring
September 30, 2026

It would seem that the install of ON1 software was incomplete. I would suggest removing all instances of ON1 and re-installing.

 

When ON1 software is installed it must download all the assets online after the initial install.

BigEricUSAAuthor
Inspiring
October 1, 2026

I’ve tried :-) They provide an Uninstaller script. Doesn’t work very well but I’ve tried it. I’ve also done a manual uninstall as well. Still crashes :-)

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices