849946 - Freeze when looking for object in Console/Inspector

Status: RESOLVED DUPLICATE of bug 820565

(DevTools :: Console, defect)

Description

[Maiko Gabriel Kinzel Engelke]

Attachment: ss (2013-03-11 at 04.23.41).png

User Agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:22.0) Gecko/20130310 Firefox/22.0
Build ID: 20130310030906

Steps to reproduce:

Inspecting a big object to check its internal values (outside of events/breakpoint, to see the current values). There is an array with a parameter used to store Google Maps markers.


Actual results:

Because Google Maps markers seems to use something like a recursive access, Firefox completely freezes for some time, then after some timeout, it comes back with an internal error, allocation size overflow.

I think it may be related because Google Maps seems to use something recursive like for storing their objects.

If I click in the message, it freezes again and then it opens the Inspector with what I want.

Each time I try to open a "sub object", it freezes again, as if recalculating everything again.


When I tried it without the markers, it worked fine, so the problem seems to not be the size, but is really this "recursion".

Didn't try it with Beta and Release, but it happened with Aurora (21).


Expected results:

List/Show the object, at least the first level.

Attached file shows the error and how Chrome shows it.

Comment 1

[Mihai Sucan [:msucan]]

Can you please provide us with the steps to reproduce the problem?

Comment 2

[Maiko Gabriel Kinzel Engelke]

It's not the same that I posted, but since it occours here too:

link: http://www.satisfeito.com/en#/
Now type SE in the console, and you will see it works normally because SE has not initialized its map.

now here: http://www.satisfeito.com/en#/estabelecimentos
Do the same thing (> SE) and it will freeze for some time and then it will give you the error.

I'm sure it's related to the marker part, cause I'm doing another Maps work and I have been changing the "Create Marker" part with a "true", just to avoid this bug (And well, I won't have the marker, but it's not a problem right now).

Comment 3

[Mihai Sucan [:msucan]]

Thanks for your report.

SE.toSource() causes the browser to freeze. You can test that in the Web Console and in the Scratchpad.

This looks like a duplicate of bug 820565.