debug.log?

Discussion and feedback on Construct 2

Post » Mon Oct 03, 2016 11:31 pm

I keep getting debug.log files put in my project's main folder. I was wondering what they meant, because they keep saying stuff like:

[1001/013324:ERROR:process_info.cc(608)] range at 0xfffde000, size 0x230 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfffdd000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfffda000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfffd7000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfffaf000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfffac000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfffa9000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfffa6000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfffa3000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfffa0000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfff9d000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfff9a000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfff97000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfff94000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfff91000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfff8e000, size 0xf84 fully unreadable
[1001/013324:ERROR:process_info.cc(608)] range at 0xfff8b000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfffde000, size 0x230 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfffdd000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfffda000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfffd7000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfffaf000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfffac000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfffa9000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfffa6000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfffa3000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfffa0000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfff9d000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfff9a000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfff97000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfff94000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfff91000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfff8e000, size 0xf84 fully unreadable
[1003/163302:ERROR:process_info.cc(608)] range at 0xfff8b000, size 0xf84 fully unreadable
B
45
S
13
G
1
Posts: 236
Reputation: 4,010

Post » Mon Oct 03, 2016 11:50 pm

Searching around the net it looks to be related to the chromium browser which nwjs is built upon. That said it appears to be a general error and many cases that cause that error have been fixed in chromium and nwjs updates.
B
92
S
32
G
110
Posts: 5,298
Reputation: 71,507

Post » Tue Oct 04, 2016 2:03 am

I have the latest version of NWJS that is available for download on this site.
B
45
S
13
G
1
Posts: 236
Reputation: 4,010

Post » Tue Oct 04, 2016 2:21 am

If your game doesn't crash they're not fatal errors. I have no idea what causes them.
B
92
S
32
G
110
Posts: 5,298
Reputation: 71,507

Post » Tue Oct 04, 2016 9:12 pm

It hasn't as far as I'm aware. Is there any way I can track down what causes them?
B
45
S
13
G
1
Posts: 236
Reputation: 4,010

Post » Tue Oct 04, 2016 10:06 pm

Not really. The errors are passively logged so it's hard to know what causes it. You could try a trial and error approach to run your game for a bit, try some things, close, and see if any errors were logged. Maybe to speed things up you could somehow check when that file is created or modified. That's something outside the scope of C2 but there are ways that can be found with google. With either approach maybe you could narrow down what causes it.

You could also use a debugger or try recompiling nw.js to stop when those errors occurs so you can check what causes it. Neither sound easy though.
B
92
S
32
G
110
Posts: 5,298
Reputation: 71,507


Return to Construct 2 General

Who is online

Users browsing this forum: Baidu [Spider], Tombas and 13 guests