Debugger crashes inspecting children

android

(Matt Robertson) #1

I’m consistently getting an app crash while inspecting children in the Locals inspector of the debugger in Water. I mentioned this bug in passing in this post about an “Error getting locals” bug, but it seems to have been unrelated since I’m still getting the crash even on the .2360 build that Marc posted for me on that thread.

Here is my Water log, starting at debugger run (as a zip because the uploader filtered out .log type):

Water.zip (897 Bytes)

And here is my test project:

com.matt.tests.zip (189.7 KB)


(RemObjects) #2

Thanks, logged as bugs://81702


(marc hoffman) #3

To be clear, Water crashes (ie terminated) completely? No “Oops something went wrong” error message dialog, just gone?

From the error I see in the log file, it should recover fine (just not show the children, ofc)…


(Matt Robertson) #4

Sorry, thanks for the question. The android app crashes and the debug session terminates. No “Oops something went wrong” error message (or any sort of message), the debug session just terminates. Water continues running as if I had manually stopped the debugger.


(marc hoffman) #5

Ah, ok. thanx!


(elenap) #6

Could you give me exact steps that leads to crashing, please. Where do you set breakpoint in your test project, what variable do you expand and so on.


(Matt Robertson) #7

I have breakpoints set at these lines:

fBoolean := true;

and

if (aParent <> nil) then

At the break on fBoolean := true; in the Locals inspector, I see savedInstanceState with a value of nil and this which refers to MainActivity and is expanded by default. The only items inside this are android.app.Activity (which can be expanded further) and fBoolean which at this point is false.

If I attempt to expand android.app.Activity then the debugger dies, after successfully expanding for about 500ms.


(Matt Robertson) #8

Any update on this? I still cannot debug with my “Locals” expanded or the debugger crashes.


(elenap) #9

We can’t reproduce your problem :frowning:
Where do you run your testcase on device or emulator?


(Matt Robertson) #10

On device. I’ve not tried an emulator, but I’ll test to see if anything changes.


(Matt Robertson) #11

Interesting. I cannot reproduce when running on an emulator.


(elenap) #12

We can’t reproduce the problem on device also. What is your Android SDK version and what Windows version do you use?


(Matt Robertson) #13

Android SDK 27 and Windows 10 v1803. The device I’m debugging on is a Pixel XL running Android Pie (9.0).


(marc hoffman) #14

Thanx. I tested here with SDK 28 on a Nexus 6P, which is, unfortunately, stuck on Oreo 8.1 :(.

For you, does the crash happen everywhere when you expect children or just for the very specific location? any chance you could post a screenshot or video of the exact steps you take/what node is selected/gets expanded, when the crash happens?

thanx!
marc