Hello, I have access violation debug error when I debug this new 8.0 JUCE program
Error message says "Access violation occured at 0x0000 "
In my desktop PC, I didn’t install DirectX
But I installed Vulkan SDK
Then, should I install DirectX on my PC to use Juce 8 API ?
Thank you
There’s no need to install DirectX; it’s built into Windows.
Can you provide more context for the error message, like a stack trace? That’s not much to go on.
Matt
Hello, Matt
The program can run all right, if I do Ctrl + F5 (run without debugging)
This source file is the just a default project created by Projucer
But if I do F5 (start debugging)
There is an exception and the debugger stopped
at the file
Drive:\JUCE\modules\juce_graphics\native\juce_DirectX_windows.h
It says, Access Violation when reading at 0x0000000000 (f_sps.dll)
Below : Calling Stack
The values at the exception
Also, I set up the juce 8 and created a default project as follows
Looks like the problem lies with that f_sps.dll. I haven’t seen that DLL before.
That DLL might be part of a Samsung DRM system?
Matt
Google points to a company called Fasoo
Seems a general problem, not only for juce:
I was just curious, nothing else to add…
Oh, I got it
It is related to Fasoo.com , their dll
That dll is related to kyobobook.co.kr e-book reader, I guess
kyobobook is a book seller company
So, If I remove kyobobook app, then that exception may disappear, I guess
But I should use e-book on my desktop.
So at this moment, if this exception cannot be solved
I better use juce 7, instead
If any of your team can help me with this issue, please let me know when you have solution, later
At now I will use juce 7
Thank you for your help and see you again, Matt
Hello, Daniel
As you said, it is related to kyobobook.co.kr e-book reader, which may use f_sps.dll
I think, I may have similar issue if I use Direct X at another project on my PC
So, at now, I will use juce 7
(And I will wait for the new solution fixing this issue later)
Thank you and have a great day, Daniel
If it is not too much trouble it would be great if you could deinstall your ebook reader, test again and report back. That way the issue can really be pinpointed to them.
You can reinstall it afterwards, it’s up to you then to choose between that ebook reader and juce 8 and any other app that mght fall into that trap.
Amazing how invasive that thing is if it can make totally unrelated apps crash. And amazing that that’s even possible in a modern OS. What sorcery is this?
I assume they are replacing system dlls with their bespoke version that intercepts certain system calls.
I can only pity everyone who has to deal with their software, voluntarily or forced by job.
I highly doubt anyone will look into this. It’s some random ebook reader software that is modifying your system. Why would the JUCE team be interested to fix this somehow (magic?). You can’t expect them to workaround an issue caused directly by a 3rd party.
OK. Right. I understand
So I just use JUCE 7, which is just fine
Thank you for your comments
At this moment, I need e-book reader, so I gave up JUCE 8
JUCE 7 is just sufficient to me
Thank you for your advise
Based on the links shared by @Daniel I would expect an update of the app you have installed might fix things for you or reach out to Faso or whoever makes your ebook reader.
Right. Thank you for your comment
But as I said, JUCE 8 or 7 is not so important to me now
JUCE 7 is just sufficient
