Hi  François;

   At the closure of this Window dialogue - are you using the CloseUserObject() method to clean up all the UO resources?

Regards  ... Chris

Do you have different buttons/functionality on each userobject?  If not you could save each datawindow either using GetFullState to a blob, or ExportJSON to a string and recreate the DWs as needed.

Francois -

   Are you running low on platfrom resources after the 5th+ OPEN call?

   I have found that for my somewhat large corporate application it will lock up when I have too many other windows open on the platform. The app behave appropriately for a while, then just freezes. Expanding the platform resources resolved this issue for us.

Olan

Hi,

First of all thank you for your answers.

No, I'm not running low on ressources, this is a new application which is still under development.

Yes, I loop for closeUserObject during the close event of the Window.

Yes, on the cirteria user object there can be anything and each one of them is different.

ExportJSON is not an option for the report DW because we have some Composite and Crosstab.

I know about the GetFullState/SetFullState which we used in a previous application but it crashes the application when the data is "large-ish".

For my tests, I open the application (either IDE or compiled version) , go straight to the report Window and open different reports (without retrieving them) this way I make sure it's not about ressources or bad cleanup.

What bothers me is that the aplication hangs and consummes CPU that is unaccounted for in the PB trace file.

I'm going to make my own timestamped trace to identify where the problem happens.

Regards,

François

There is an internal debugger that can be used, but not sure how much help it may be. It's undocumented and might take some trial and error to see which options give you the most output from object creation. Turning on the debugger will open a console window with results of current activities. DO NOT CLOSE THIS WINDOW, it will immediately end whatever you have running in the IDE or compiled EXE without any warning, and no events will be fired (it's like sending 'kill -9' in the *nix world, or "end task" in windows task manager).

/*
1 - turn on logging console (warning, closing this will close PB dev env with no warnings or close events getting triggered, ditto for running exe)
3 - show memory related calls
20 - show internal calls
21 - pbl management - by itself, doesn't create log
23 - show internal calls
26 - show internal calls
27 - function pointer loading, structure pointer assigns
29 - object group processing
30 - show function/event calls
31 - show pcode trace
32 - show external func calls
34 - show pcode line execution
38 - event queue processing
42 - show internal calls
43 - global symbol references dump
44 - class ref
45 - routine symbol table dump
*/
int ii_options = {1, 30, 32, 34}  // set this to whatever combination of flags you want from the above list

long l
sting ls_filename = "rt_debug.txt"

l = rt_dbg_outfile(ls_filename) // debug output file is required, or nothing works
for l = 1 to upperbound(ii_options)
	rt_dbg_set(ii_options[l])
next
l = rt_dbg_on()			// enable rd_debug

// open objects here

// clean up
for l = 1 to upperbound(ii_options)
	rt_dbg_del(ii_options[l])
next
l = rt_dbg_off()		// disable rt_debug

Thanks Brad, I did not know about the rt_dbg_outfile

But it slow the application so much that I can't get any good informations out of it.

"Funny" thing happening in the window

for each report I have a report datawinwond and optionnaly two userobjects

The window will either display the report or the userobjects

I have a toggle button to switch what I display.

Appart from always displayed objects in the window I'll display either one report DW or two user objects

the other objects in the arrays are hidden

After a very few report have been openened the first time I hit the toggle button to swtich from one view to another for a repport the application hangs a few seconds. Then it all goes smoothly the next time I hit the switch for that report.

If I open another report and go back to a report where I previously hit the switch it goes smoothly too.

Now if I open my objects outside of the visible area of the window I don't experience the freeze time when hitting the toggle button (in that case it will move the objects into or outside the visible area along with the .visible=true/false).

that makes me think that the freeze might have something to do with drawing the screen.

Even if I open my objects outside the visible area I still experience the delay after the opening of the objects.

Tried to play with setRedraw but no luck.