XojoGUIFramework32.dll exception (Desktop/Windows)

General
1

I got XojoGUIFramework32.dll exception on Windows 2008 when I ran myapp.exe there.
I built the binary by using 2015R2.

From the system requirements, I can only see below ones.
Windows Vista
Windows 7
Windows 8.x
Windows 10

Does it mean that I can’t run myapp.exe on Windows 2008?

2

I’m guessing you are talking about Windows Server 2008 and I haven’t had any problems running my Xojo apps in that environment. You’re not trying to run a GUI app on the windows core product are you?

3

What do you mean “windows core product”?

4

From 2008 onward you can install a Windows core installation which doesn’t have a GUI interface. A typical Hyper-V installation will be installed in this mode. The win32 components aren’t installed, so won’t be available.

5

Ah…
Probably, I just installed W2008 with the mode. I just prepared the server quickly so I made it simple.
I think you are right.

Thank you so much!!!

6

Hi,

Even though I reinstalled W2008 Enterprise Edition, I got the same issue.

APPCRASH
XojoGUIFramework32.dll

Anyone has this issue on W2008?

Thanks.
Changwon.

7

Exception code is c0000005.
How can I debug this issue?

8

Did you copy the libs folder along with the executable file?

9

Yes.
My installer does that job, and I can see XojoGUIFramework32.dll file under libs folder.

Just in case:
I use RubberView in my Windows application.

10

When I try to run the Application with IDE, I got “OutOfMemoryException”.
I also use a Jeremie customer UI, and below stack shows the name of it such as UI_PopupMenu, UI_listbox.

I think the Crash(XojoGUIFramework32.dll) issue is related to this “OOB” exception as the exception code is c0000005 in crash stack(with a real application, not IDE).

I am wondering why this issue happens only in W2008 although there is enough free memory.

2016-05-06 07:38:12 : OutOfMemoryException


MemoryBlock.Constructor%%o<MemoryBlock>i4
UI_PopupMenu.StringToPicture%o<Picture>%o<UI_PopupMenu>s
UI_PopupMenu.Event_Open%%o<UI_PopupMenu>
UI_Control.Event_Open%%o<UI_Control>

Application._CallFunctionWithExceptionHandling%%o<Application>p




Window.Constructor%%o<Window>
MainWindow.MainWindow%o<MainWindow.MainWindow>%
ProductKeyModule.CopyChartsResources
App.ProductkeyControl%%o<App>
App.Event_Open%%o<App>

Application._CallFunctionWithExceptionHandling%%o<Application>p



REALbasic._RunFrameworkInitialization%%p
_Main

2016-05-06 07:38:12 : OutOfMemoryException


MemoryBlock.Constructor%%o<MemoryBlock>i4
UI_Listbox.UI_Listbox.StringToPicture%o<Picture>%o<UI_Listbox.UI_Listbox>s
UI_Listbox.UI_Listbox.Event_Open%%o<UI_Listbox.UI_Listbox>

Application._CallFunctionWithExceptionHandling%%o<Application>p
11

@ Issues

  1. With Xojo 2016R1 / IDE / As soon as I start an application / OutOfMemoryException on various Jeremie custom UI controls.
  2. With Xojo 2015R2 / IDE / When I close(click ‘x’) an application / XojoGUIFramework32.dll crash

My main framework is 2015R2, so I tried to find the problematic place and I seem to find the one.

There is a code in App.close I wanted to clear memory/array/controls and so on.
Below is the one of them.

MainWindow.ConfigurationScreen.CheckTimer.Enabled=False

Strangely, after commenting the code above, I don’t see #2 issue in Xojo 2015R2.
Actually, I don’t need to have the code. -.-

Tried also to put above code in a simple application but can’t reproduce the issue there.

I have no idea what is something wrong in the code but at least when I close the application, I don’t see XojoGUIFramework32.dll error anymore.
(Just in case, this issue only happens to me with W2008 64bit)

Thanks.