New issue
Advanced search Search tips

Issue 729414 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Nov 2017
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Construct 3 - browser crashes when trying to preview Grokar demo

Reported by tript...@gmail.com, Jun 4 2017 
Steps to reproduce the problem:
1. got to editor.construct.net on an Nvidia Shield tablet
2. open the Grokar demo project
3. press "preview" button

What is the expected behavior?
The project should load and play 

What went wrong?
the splash screen shows for an instant, then the "aw snap" window shows.

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 7.0
Flash Version: 

The system information is captured in this bug on the Construct site - however this is a memory management issue so it's the browser tab that's crashing.  https://github.com/Scirra/Construct-3-bugs/issues/436

Comment 1 by tript...@gmail.com, Jun 4 2017 

More system info of the tablet involved. 
Platform information
Browser: Chrome
Browser version: 58.0.3029.83
Browser engine: Blink
Browser architecture: 32-bit
Context: browser
Operating system: Android
Operating system version: 7.0
Operating system architecture: 32-bit
Device type: mobile
Device pixel ratio: 2
Logical CPU cores: 4
User agent: Mozilla/5.0 (Linux; Android 7.0; SHIELD Tablet K1 Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.83 Safari/537.36
C3 release: r34

Comment 2 by tript...@gmail.com, Jun 5 2017 

Note it's "Glokar" not Grokar...

Comment 4 by tript...@gmail.com, Jun 7 2017 

I'll reproduce it and add the crash ID.

Comment 5 by tript...@gmail.com, Jun 8 2017 

I tried the same actions in Chrome Canary 61.0.324.3 and cannot reproduce. I assume this means that eventually regular chrome will pick up whatever memory fix you did so perhaps this is no longer an issue.

Comment 6 by pnangunoori@chromium.org, Nov 16 2017

Status: WontFix (was: Unconfirmed)
Marking this issue as WontFix as per the Comment #5.

@triptych - Please feel free to file a new issue if the issue is observed in the latest Chrome builds.

Thanks!
►

Sign in to add a comment