Major Selection Error Occurred

hey, neato, the system turned all those links into real links I get to see some of the base code of this game, I think.

I see JavaScript.

I see dead people.

I see me working at Bytro as one of the developers. Because I can actually understand this mess.

I have seen this problem on my FP game as well, but I had a similar problem when the page loaded, sucks

Diabolical wrote:

hey, neato, the system turned all those links into real links I get to see some of the base code of this game, I think.

I see JavaScript.

I see dead people.

I see me working at Bytro as one of the developers. Because I can actually understand this mess.

Alphared wrote:

Diabolical wrote:

hey, neato, the system turned all those links into real links I get to see some of the base code of this game, I think.

I see JavaScript.

I see dead people.

I see me working at Bytro as one of the developers. Because I can actually understand this mess.

It's only showing you the 'get' property transferred by the HTML to the server... no code here.

Unrelatedly, I must ask, how can you have negative 995 points rating in the forum?

Diabolical wrote:

Alphared wrote:

Diabolical wrote:

hey, neato, the system turned all those links into real links I get to see some of the base code of this game, I think.

I see JavaScript.

I see dead people.

I see me working at Bytro as one of the developers. Because I can actually understand this mess.

It's only showing you the 'get' property transferred by the HTML to the server... no code here.

Yeah, inside the spoiler is a bunch of "notify" and "publish" commands with link properties and other stuff. The WYSIWYG editor converted these into clickable links. Try one and you'll see a bunch of JavaScript and other stuff. For example, this one will show you what might be the main server code for the game and is about a 4 MB file of pure JavaScript. http://www.callofwar.com/ww2-dev/js/main-built-min.js

Unrelatedly, I must ask, how can you have negative 995 points rating in the forum?

AND, I don't know, I guess people just don't like me.

Alphared wrote:

Then, that would be another bug - and it could compromise the security of the game

AND, I don't know, I guess people just don't like me.

As for the bug, I am a programmer, and -- in theory -- I could glean a lot from this bug. And I could reverse engineer the structure of the game as much as is indicated by the code that is accessed. Does this bug reveal the whole code or just a portion? I don't know. But I'm ethical enough not to do anything to Bytro. Others might not be.

I wish they'd release the code for modding purposes to the game community, anyway. They can still retain copyright and make lots of money while letting the players improve the game (which would draw in and retain more users...to Bytro's benefit).

Of course the modding parts would need to be superficial to the core base -- changing the database and game rules without affecting how the game functions. Usually, a full code base release isn't done until a developer has set aside active development of a project, but there are rare and special cases where they still maintain and improve code that is fully mod-able. A classic example of that is the later editions from the civilization series.

Of the code that is accessible, unless I spend some time reviewing the visible code, I wouldn't even know if it includes base functionality or is just purely interaction script. But if I were programming the thing, I'd keep the base as a fully compiled core with only the server interactive portions in JavaScript. Perhaps that is the case here, anyway.

Wow

This Bug happened again. This time while trying to build something in a factory in a different province. After happening twice, now, I'm thinking that the null reference is to a bad address in the database on the server end. Not sure, though, that's for the developers to decide. But, if this is a memory issue, they may have a huge task of tracking down where a potential memory leak or bad offset is occurring and that is a major bitch of an issue. I kinda feel bad for the developers right about now.

I've never seen this error in a non-Frontline game. So, hopefully, they can rollback the memory management and database management to find where the address alignment may differ. Aside from that, apart from rote automation, I don't know how else to advise them on finding where the address breaks.

However, I've just had another thought on this that might help. Though I doubt this is the case, one should look for every possible cause. The broken address idea may not necessarily be what's wrong. Of course there could potentially be any number of reasons for the null entry. But there is a possible simpler explanation in this: There could be a glitch in the data transfer integrity between client and server such that error-checking on the server end is missing a failed transfer from the client. The Internet may be dropping a packet somewhere and the server could have an error that isn't noticing this or a similar problem and so it tries to retrieve database or memory information using an incorrect address (or no address...as some kind of a fail-safe to protect existing current data in memory).

Regardless of what the error is, I would like not to have to see this message again. These types of errors should not be encountered beyond the in-house white-box testing. That they are making it to the Frontline testers is an indication that the dev team needs to do a better job of improving their test case development. Address issues should never even get as far as a black-box test and this just goes to show that this bug may be a sign of a huge break in the code from a recent update by them.

----

this.getProperties(...) is null

ultshared.UltProvince.prototype.getQueueableUpgrades@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:40295:22

hup.ProvinceSelectionModel.prototype.intersectQueueableUpgrades@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54859:25

hup.ProvinceSelectionModel.prototype.updateIntersectedProperties@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54780:5

hup.ProvinceSelectionModel.prototype.updateProvinces@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54769:9

hup.ProvinceSelectionModel.prototype.getIntersectedProvince@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54613:7

hup.ui.ProvinceProductionsModel.prototype.getCurrentConstructions@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:75513:16

hup.ui.ProvinceProductionsWidget.prototype.getMainModel@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76147:34

hup.ui.ProvinceProductionsWidget.prototype.updateContent@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76130:58

hup.ui.ProvinceProductionsWidget.prototype.onProvinceSelected@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76516:7

notify@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:263:7

publish@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:333:11

hup.ProvinceSelectionModel.prototype.setSelected@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54500:7

hup.MapMouseController.prototype.onSelectionClick@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:69845:11

hup.MapMouseController.prototype.onMouseUp@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:69796:13

hup.ui.MapWidget.prototype.registerMouseListeners/<@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:70261:14

x.event.dispatch@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:5:9954

x.event.add/y.handle@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:5:6772

Details:

TypeError: this.getProperties(...) is null

----

this.getProperties(...) is null

ultshared.UltProvince.prototype.getQueueableUpgrades@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:40295:22

hup.ProvinceSelectionModel.prototype.intersectQueueableUpgrades@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54859:25

hup.ProvinceSelectionModel.prototype.updateIntersectedProperties@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54780:5

hup.ProvinceSelectionModel.prototype.updateProvinces@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54769:9

hup.ProvinceSelectionModel.prototype.getIntersectedProvince@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54613:7

hup.ui.ProvinceProductionsModel.prototype.getCurrentConstructions@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:75513:16

hup.ui.ProvinceProductionsWidget.prototype.getMainModel@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76147:34

hup.ui.ProvinceProductionsWidget.prototype.updateContent@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76130:58

hup.ui.ProvinceProductionsWidget.prototype.onProvinceSelected@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76516:7

notify@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:263:7

publish@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:333:11

hup.ProvinceSelectionModel.prototype.setSelected@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54500:7

hup.ProvinceSelectionModel.prototype.updateSelection@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54531:5

notify@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:263:7

publish@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:333:11

ultshared.UltMapState.prototype.publishUpdate@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:41287:5

hup.GameStateHandler.prototype.sendUpdateNotification@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:46527:9

hup.GameStateHandler.prototype.onMessage@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:46385:21

notify@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:263:7

publish@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:333:11

lzr.Server.prototype.onMessage@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:3226:5

lzr.AjaxServer.prototype.onMessage@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:3338:5

x.Callbacks/l@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:4:24877

x.Callbacks/c.fireWith@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:4:25702

k@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:6:5346

.send/t/<@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:6:9152

Details:

TypeError: this.getProperties(...) is null

----

this.getProperties(...) is null

ultshared.UltProvince.prototype.getQueueableUpgrades@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:40295:22

hup.ProvinceSelectionModel.prototype.intersectQueueableUpgrades@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54859:25

hup.ProvinceSelectionModel.prototype.updateIntersectedProperties@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54780:5

hup.ProvinceSelectionModel.prototype.updateProvinces@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54769:9

hup.ui.ProvinceProductionsWidget.prototype.onMapUpdate@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76496:7

notify@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:263:7

publish@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:333:11

ultshared.UltMapState.prototype.publishUpdate@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:41287:5

hup.GameStateHandler.prototype.sendUpdateNotification@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:46527:9

hup.GameStateHandler.prototype.onMessage@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:46385:21

notify@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:263:7

publish@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:333:11

lzr.Server.prototype.onMessage@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:3226:5

lzr.AjaxServer.prototype.onMessage@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:3338:5

x.Callbacks/l@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:4:24877

x.Callbacks/c.fireWith@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:4:25702

k@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:6:5346

.send/t/<@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:6:9152

Details:

TypeError: this.getProperties(...) is null

Diabolical wrote:

This Bug happened again. This time while trying to build something in a factory in a different province. After happening twice, now, I'm thinking that the null reference is to a bad address in the database on the server end. Not sure, though, that's for the developers to decide. But, if this is a memory issue, they may have a huge task of tracking down where a potential memory leak or bad offset is occurring and that is a major bitch of an issue. I kinda feel bad for the developers right about now.

I've never seen this error in a non-Frontline game. So, hopefully, they can rollback the memory management and database management to find where the address alignment may differ. Aside from that, apart from rote automation, I don't know how else to advise them on finding where the address breaks.

However, I've just had another thought on this that might help. Though I doubt this is the case, one should look for every possible cause. The broken address idea may not necessarily be what's wrong. Of course there could potentially be any number of reasons for the null entry. But there is a possible simpler explanation in this: There could be a glitch in the data transfer integrity between client and server such that error-checking on the server end is missing a failed transfer from the client. The Internet may be dropping a packet somewhere and the server could have an error that isn't noticing this or a similar problem and so it tries to retrieve database or memory information using an incorrect address (or no address...as some kind of a fail-safe to protect existing current data in memory).

Regardless of what the error is, I would like not to have to see this message again. These types of errors should not be encountered beyond the in-house white-box testing. That they are making it to the Frontline testers is an indication that the dev team needs to do a better job of improving their test case development. Address issues should never even get as far as a black-box test and this just goes to show that this bug may be a sign of a huge break in the code from a recent update by them.

----

this.getProperties(...) is null

ultshared.UltProvince.prototype.getQueueableUpgrades@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:40295:22

hup.ProvinceSelectionModel.prototype.intersectQueueableUpgrades@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54859:25

hup.ProvinceSelectionModel.prototype.updateIntersectedProperties@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54780:5

hup.ProvinceSelectionModel.prototype.updateProvinces@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54769:9

hup.ProvinceSelectionModel.prototype.getIntersectedProvince@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54613:7

hup.ui.ProvinceProductionsModel.prototype.getCurrentConstructions@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:75513:16

hup.ui.ProvinceProductionsWidget.prototype.getMainModel@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76147:34

hup.ui.ProvinceProductionsWidget.prototype.updateContent@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76130:58

hup.ui.ProvinceProductionsWidget.prototype.onProvinceSelected@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76516:7

notify@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:263:7

publish@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:333:11

hup.ProvinceSelectionModel.prototype.setSelected@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54500:7

hup.MapMouseController.prototype.onSelectionClick@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:69845:11

hup.MapMouseController.prototype.onMouseUp@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:69796:13

hup.ui.MapWidget.prototype.registerMouseListeners/<@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:70261:14

x.event.dispatch@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:5:9954

x.event.add/y.handle@https://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:5:6772

Details:

TypeError: this.getProperties(...) is null

----

this.getProperties(...) is null

ultshared.UltProvince.prototype.getQueueableUpgrades@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:40295:22

hup.ProvinceSelectionModel.prototype.intersectQueueableUpgrades@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54859:25

hup.ProvinceSelectionModel.prototype.updateIntersectedProperties@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54780:5

hup.ProvinceSelectionModel.prototype.updateProvinces@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54769:9

hup.ProvinceSelectionModel.prototype.getIntersectedProvince@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:54613:7

hup.ui.ProvinceProductionsModel.prototype.getCurrentConstructions@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:75513:16

hup.ui.ProvinceProductionsWidget.prototype.getMainModel@http://www.callofwar.com/ww2-dev/js/main-built-min.js?bust=1470660687:76147:34

hup.ui.ProvinceProductionsWidget.prototype.updateContent@http://www.callofwar.com/ww2-

Hell, Id say you can run the servers better than anyone haha

You flatter me, sir.

Forwarded to devs.

I got a reply from Doc Leprechan ... he says its a known issue.