Sorry for all the thread updates. If I need to be using a different method to communicate let me know.
In an earlier thread a few weeks ago I mentioned a crashing issue in 1.02.21 that occurs when you try to refer to some key page variables used by WD.
There are a couple threads about this created by other users in this forum as well.
One key variable is called act-browselist-X where x represents a number between 0 and the total number of thumbs present on a given browse page (video browsing for example).
If the value is zero, it means the thumb is not selected. If it is one, it means it is selected.
In 1.02.21, referring to these variables to determine which thumb is presently active works "most" of the time but every so often it causes the DMAOSD to crash, requiring a WD reboot.
I got around this issue by writing some C code to examine the heap used by WD to locate the page variables myself.
I tested this on the 1.05.04 release and it crashes almost immediately (usually only takes a couple of references before DMAOSD crashes). The interesting thing is that if you try to read an undefined page variable, you simply get a NULL value but no crashing. For some reason, these special page variables cause a crash even when they do exist and are used by WD.
Here is a snippet of the plugin code that will cause a crash within a few references (when it does work it returns the right value):
- Code: Select all
zactive = Page.Top.getParam("act-browselist-0");
if (zactive > 0)
this.debug.Log("In PageKey function and thumb 0 is active!", 1);