Page 1 of 1

Memory corrupt error on Win 64 (Even sample projects)

Posted: Sat Apr 14, 2012 1:22 am
by ricovox
I have a licensed (PAID) version of F-In-Box (v3.3.3.6)
I recently tried to run a program I developed using F-in-box on a PC running Windows 7 x64.

I received the following error: "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

I also tried the F-In-Box samples (.Net, C#). ALL OF THE SAMPLES had the same error. I then downloaded the newest release (v3.3.3.8). I again tried to run the samples, using the NEW version of F-in-Box and all of them had the same error!

So this error has nothing to do with the host application code, and newer versions of F-in-box do not fix the problem.

The stack trace of the first SAMPLE project is below:

at f_in_box__lib.f_in_box__wrapper.FPC_GetClassNameW(UInt32 hFPC)
at f_in_box__lib.f_in_box__control.get_CreateParams()
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Control.get_Handle()
at f_in_box__lib.f_in_box__control.set_FlashProperty_AlignMode(Int32 value)
at Sample01_SWF_And_FLV_Player.MainForm.InitializeComponent() in C:\Users\Richard\Desktop\Sample01_SWF_And_FLV_Player\Form1.cs:line 155
at Sample01_SWF_And_FLV_Player.MainForm..ctor() in C:\Users\Richard\Desktop\Sample01_SWF_And_FLV_Player\Form1.cs:line 35
at Sample01_SWF_And_FLV_Player.MainForm.Main() in C:\Users\Richard\Desktop\Sample01_SWF_And_FLV_Player\Form1.cs:line 213
at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

It looks like FPC_GetClassNameW is the culprit.
Thanks for any help you can provide.

P.S. Of course these projects are all run as x86 projects (under WoW64)

Related to Flash Version?

Posted: Sat Apr 14, 2012 3:22 am
by ricovox
Just an update on the issue I described above.

I didn't mention in my previous post, but the memory corruption error I got occurred each and every time the F-in-Box Form was created, even in the F-in-box sample projects. So the error is a major one, that occurred 100% of the time, as soon as an F-in-box Form was instantiated.

I also didn't mention it, but I had the latest version of Adobe Flash Player installed (v

My system is Windows 7 Ultimate x64, so the version of Flash player I installed was the 64-bit version (which also includes the 32-bit version according to Adobe). The flash plugin worked fine from 32-bit Firefox, so I assumed that nothing was wrong with the Flash plugin. But just to verify this, I uninstalled flash and installed only the 32-bit version (still Again, I got the same memory corruption errors. So I uninstalled that version, and installed an older version of Flash Player (v11.1.102.55). That fixed the problem completely!

So just a heads up, that the newest version of Flash Player may cause some issues on certain platforms.

Just to summarize:

Flash (64bit+32bit) FAILED
Flash (32bit) FAILED
Flash (32bit) WORKED

Posted: Fri Apr 27, 2012 7:44 am
by Softanics

Going to check it.

Thank you!

Posted: Fri Apr 27, 2012 7:52 am
by Softanics

Can't reproduce, so I'm writing to you to get more help...

Thank you!

Posted: Tue May 15, 2012 3:41 pm
by Softanics

At last we've reproduced the issue. The update will be available soon.

Thank you.


Posted: Wed Aug 22, 2012 5:31 pm
by ricovox

Thank you for looking into this.

My client purchased a license for F-In-Box program in the past. Would he need to pay again to get the updated version?

Can you please post an explanation and possibly a work-around for .Net developers who are experiencing this problem?

I experience this problem intermittently, and I don't quite know why or what causes it. It is hard to reproduce, but it happens to my client on a regular basis (after playing about 10 to 20 flv or swf files with f-in-box).

Here is my latest bug trace:

Code: Select all

AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at f_in_box__lib.f_in_box__wrapper.FPC_GetClassNameW(UInt32 hFPC)
   at f_in_box__lib.f_in_box__form.get_CreateParams()
   at WindowsTutorial.FlashCanvas.get_CreateParams()
   at System.Windows.Forms.Control.CreateHandle()
   at System.Windows.Forms.Form.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Control.set_Visible(Boolean value)
   at f_in_box__lib.f_in_box__form.set_ShowInTaskbar(Boolean value)
   at WindowsTutorial.FlashCanvas..ctor()

It occurred when I created a new window derived from the F-in-box form. (My window is called FlashCanvas, as you can see in the Exception trace). I had recently closed a similar window, so maybe it has something to do with WndProc messages being sent to the old window or something like that.

But you said you were able to reproduce and fix this, so please fill us in on the details.


Posted: Wed Aug 22, 2012 5:39 pm
by ricovox
And here is another Exception Trace.
I'm posting this one because the source of the exception is different than the first, and I'm not sure if this is a separate bug or the same one.

Code: Select all

AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at f_in_box__lib.f_in_box__wrapper.FPC_LoadRegisteredOCX()
   at f_in_box__lib.AxCode..ctor()
   at f_in_box__lib.f_in_box__form..ctor()
   at WindowsTutorial.FlashCanvas..ctor()

Posted: Tue Aug 28, 2012 3:16 pm
by Softanics

I've just answered to your ticket.

Thank you.