asdf
@Mitabre - I'd avoid 3rd party sites, especially since DVDFAB relies on customers downloading from them. Also, by downloading from DVDFAB, you rule out the possibility of someone tampering with the executable, not to mention viruses, etc.
@reeman - According to the evidence I've found, at least in my case, QT is having an issue accessing a memory space. An access violation occurs when a program is trying to access a piece of RAM that has already been assigned to another application or the wrong data type exists in that memory space - like a letter exists instead of a number. This can happen for a variety of reasons and can be quite the pain in the ass to debug, especially without feedback for the developer. I suspect the developers immediately knew it's got something to do with QT.
Access violations aren't exactly planned on, so the app in question generally takes a dump, but usually there's a log file or SOMETHING to go on. Luckily, "Bugtrap" caught this info.
What's weird is that my first reaction is not to blame the QT .dll. From the looks of it, it's a DVDFAB object that's using QT: QMUTEX::lock. But I'm not an expert. Could be an uninitialized variable - (producing garbage or wrong data type).
@Mitabre - I'd avoid 3rd party sites, especially since DVDFAB relies on customers downloading from them. Also, by downloading from DVDFAB, you rule out the possibility of someone tampering with the executable, not to mention viruses, etc.
@reeman - According to the evidence I've found, at least in my case, QT is having an issue accessing a memory space. An access violation occurs when a program is trying to access a piece of RAM that has already been assigned to another application or the wrong data type exists in that memory space - like a letter exists instead of a number. This can happen for a variety of reasons and can be quite the pain in the ass to debug, especially without feedback for the developer. I suspect the developers immediately knew it's got something to do with QT.
Access violations aren't exactly planned on, so the app in question generally takes a dump, but usually there's a log file or SOMETHING to go on. Luckily, "Bugtrap" caught this info.
What's weird is that my first reaction is not to blame the QT .dll. From the looks of it, it's a DVDFAB object that's using QT: QMUTEX::lock. But I'm not an expert. Could be an uninitialized variable - (producing garbage or wrong data type).
Comment