Entraides et échanges autour de la technologie Scol - Informations and exchanges on the Scol technology
Vous pouvez changer la langue de l'interface une fois inscrit - You can change the language once registered
You are not logged in.
while working on my mediaoctopus3d player project, i find that after closing the player down (I think I destroy all resources that I create, bitmaps, alphabimaps, comptext elements, etc), scol.exe *32 remains running after i shut the player down.
even if i right click and exit the scol vm on the system tray, only one process is removed and the rest of the processes, (8 at the moment) remain running in the task manager.
is this a sign that i'm not destroying resources?
thx for your help
-h
Offline
Do you perform a _closemachine after freeing all your resources ? If not, give it a try.
Offline
Do you perform a _closemachine after freeing all your resources ? If not, give it a try.
thx for your reply Bob and hello.
yes i call that function when mainWindow (the same as the global variable in os3dplayer.pkg) gets shutdown:
fun cbV3DdsMainWin(winstr,octoplayerstruct)=
dsEdCtrlButton octoplayerstruct.OCTOPLAYER_openfilebuttonabutton;
dsEdCtrlButton octoplayerstruct.OCTOPLAYER_openurlbuttonabutton;
dsEdCtrlButton octoplayerstruct.OCTOPLAYER_closeplayerbutton;
_DSalphaBitmap octoplayerstruct.OCTOPLAYER_openurlbuttonabitmap;
_DSalphaBitmap octoplayerstruct.OCTOPLAYER_openfilebuttonabitmap;
_DSalphaBitmap octoplayerstruct.OCTOPLAYER_closeplayerbuttonabitmap;
dsEdWindowToolBar mainWindow octoplayerstruct.OCTOPLAYER_main_toolbar;
_closemachine;
0;;Offline
This is strange ...
If you quit the Voyager, do all the other scol.exe processes disappear ? (Normally, they should)
Is it the first time you encounter this problem ?
- If you're sure that it is the first time, then the problem certainly lies in some code you added/modified recently. Try to check this.
- If you're not sure, then it'll be a bit more complicated to identify the source of the problem.
You can try to remove (comment) parts (one block by one block) of your code and see if the problem disappears or not. When the problem disappears, then the problem is in the last block of instructions that you commented.
I hope this helps.
Offline
8 process ? you should only have 2 when you start your player
the voyager and your player.
can you try with the beta version of the voyager ?
Offline
8 process ? you should only have 2 when you start your player
the voyager and your player.can you try with the beta version of the voyager ?
This behavior stopped after I cleaned up my code.
Offline
These processes could be also old VMs if your machine has not been down since a long time.
Like Bob says, you should always add _closemachine (or _closechannel in few cases) after freeing all resources : this frees all internal datas and properly exits the VM.
After _closemachine, it is useless to write a statment, even 0 (_closemachine returns 0 itself).
Furthermore, if Scol is in "developer mode", the primary VM (the Voyager) is not down : so, in this case, one scol.exe keeps and runs even if no Scol applications is launched. To know if this mode is activated, please open the Scol settings interface (right click on the Scol icon and "Settings"). For exit it, you should click on the Scol icon and select the exit item properly.
Likewise, you can exit a Scol application which doesn't respond by clicking on the Scol icon : choose "Advanced" next "Control Panel". Select the application name and click on "Stop". If this way is inefficient, try by the Windows systray tasks manager.
Offline
This behavior stopped after I cleaned up my code.
This behavior can occur when an application crashes without console (or before the call of _showconsole) and/or the Scol maintenance settings is off.
Indeed, the VM can not properly exit and the process is not terminate by the OS.
Offline