4 ms·
My crashes were definitely due to Adobe. It was latest updated Windows, Nvidia card with latest drivers, latest adobe, plenty of free space and RAM, etc. It cra
by Erlich_Bachman 7y ago
My crashes were definitely due to Adobe. It was latest updated Windows, Nvidia card with latest drivers, latest adobe, plenty of free space and RAM, etc. It crashed even without any plugins.
Also as an additional thought, is it really that good that they make such a big software that can be crashed because of a plugin? They know there will be a plugin Zoo out there, they know the plugins sometimes have to use GPU on their own, which brings many troubles with drivers etc, - they still can't manage to just isolate in in their own processes? Plugins are used all the time, it's an industry of itself. Company of the size of Adobe can't foresee that some plugins will be unstable and they need to take care of it? The dreaded chrome can isolate websites in their own processes, Adobe can't do the same with a mere plugin??
- justinclift 7y agoJust to check, did you run a full memory check / burn in test on the computer? eg memtest86 or similar Sometimes this kind of thing turns out to be memory with a problem at some address. :/
- Erlich_Bachman 7y agoCould always be a good think to check, thank you. This thing happen on different hardware for me though, reliably.
- colejohnson66 7y agoLinusTechTips had a weird bug with some Adobe product (I think Premiere) where, IIRC, it crashed if the project was read off the disk too fast
- Erlich_Bachman 7y agoI've had projects where literally just opening the project and scrolling through it (moving the cursor) crashed the program reliably within 20 seconds/10-20 scrollings. This made me think their QA is a joke at this point.