Stack Overflow Error after update

Strange issue. I upgraded my firmware on my Edge 530 to 7.0.0 and my app crashed on start. I upgraded my SDK/device simulator to the latest version, rebuilt and it runs fine on the sim but when I deploy to the real device, the error is still there. The post mortem info is

---
Error: Stack Overflow Error
Details: 'Failed invoking <symbol>'
Time: 2021-01-06T10:39:46Z
Part-Number: 006-B3121-00
Firmware-Version: '7.00'
Language-Code: eng
ConnectIQ-Version: 3.2.3
Store-Id: 07a52d1d-4b06-42be-b9da-5cb2a92fc938
Store-Version: 62
Filename: A9QH3609
Appname: MenoX
Stack:
- pc: 0x10009478
- pc: 0x10009478

0x1009478 is DEC 268473464 and corresponds about to

ConfigFactory looks like

class ConfigFactory {

	hidden var screenHeight = System.getDeviceSettings().screenHeight;
	hidden var screenWidth = System.getDeviceSettings().screenWidth;

	function getEdgeChargeBarConfig() {
		var config = new EdgeChargeBar.Config();
		config.boundaries = [
			0, 
			screenHeight - 10, 
			screenWidth, 
			screenHeight
		];
		return config;	
	}
		
}

is <init> the calls to the System.getDeviceSettings() ?

Pointers appreciated. It's a bit hard to track down the issue when it happens so soon in the initialization...

I also tried mining the application entry class methods with System.println but I didn't get anything in the log file. It's supposed to be a A9QH3609.txt in my beta-app case, right?

0 jim_m_58 over 5 years ago

How tight on memory are you per the sim? Is it working in the sim?

0 Nik over 5 years ago in reply to jim_m_58

Works in the simulator, says 134.7 / 1019.6.

0 Nik over 5 years ago in reply to Nik

It broke the first time I tried when 7.0.0 came out but it's off-season for me so didn't return until now. The old app worked fine so shouldn't be any 3.2.x usage in there (and 7.0.0 should support that anyway, right). My re-build targetted 3.2.x directly

A SOE would be strange for and OOM error(?)

0 jim_m_58 over 5 years ago in reply to Nik

What about "peak" in the memory viewer?

0 Nik over 5 years ago in reply to Nik

On an unrelated(?) note, I updated my old Forerunner 235 and the Dozenrun (or something like that) also bombed out direcly

0 Nik over 5 years ago in reply to jim_m_58

Umm. When I started the session the app died in the simulator, too. Didn't increase the mem usage before throwing in the towel, though.

0 Nik over 5 years ago in reply to Nik

Now I'm even more confused. My landing page has an input delegate that moves to the main view when pressing the start button. I have something like

   	function onKey(evt) {
   		var key = evt.getKey();
System.println(key + " " + WatchUi.KEY_START);   		
   		if (key == WatchUi.KEY_START) {
  			var view = new MainView(controller);
  			var delegate = new MainInputDelegate(controller);
  			controller.confirmSession();
	   		WatchUi.switchToView(view, delegate, WatchUi.SLIDE_DOWN);
   		}
	}

but I get 5 18 and never go to the main view. And even then, it should do nothing and not crash

0 jim_m_58 over 5 years ago in reply to Nik

One thing I see is you are failing to return true/false based on what you've handled.

0 Nik over 5 years ago in reply to jim_m_58

It must have been working by accident then. Anyway, If I change the if to key == 5 I see the main view half-rendered and then it crashes without any information

0 jim_m_58 over 5 years ago in reply to Nik

It has gotten more strict since the va3. Add proper returns in onKey and try again.