Using getParam crashes the box

[Darren]

I've been trying out page.getParam, but I can't seem to read any variables without it crashing the box. Sometimes I can read a number of variables before the crash, other times it crashes on the first usage. This happens when trying to read pagecounter, browselist_X_text, info_cur_time, and others too. Using a try-catch does not stop the crashes from happening, and no error is ever caught.

Due to when some of the variables are actually populated with values (pagecounter, browselist_X_text) the only event that I've found where they do have values is the onPageTimer event, but that is more like polling than being event driven. Is there an onLoad or onChange event that I can use?

Is it safe to use getParam on variable names that either don't exist, or don't have a value? And is there any multi-threading going on behind the scenes? Is getParam thread-safe? The intermittent crashing I'm seeing reminds me of that.

I'm using WDTVExt-Live-0.23.5 with WDLXTV_LIVE-0.4.2.0.

Thanks

[CrashX]

I believe b-rad has the same issue and it is currently being looked into by pibos.

[arifg]

Have you tried :

Code: Select all

if(some_variable != undefined)
  do_something(some_variable);


?

[Darren]

Thanks for the suggestion. However, the page variables can't be accessed directly. You must use page.getParam('var') to retrieve their contents. And since the try/catch is not actually catching the problem then this indicates the problem is likely within the getParam function itself, which exists outside the js environment.

[arifg]

However, the page variables can't be accessed directly

Sorry for misunderstanding: I had a similar issue with sporadic crashes recently, investigation leaded me to the problem with accessing page.markupFileName from onPageTimer so I decided you have the same. You your case, seems like you're right. Unfortunately.