Created attachment 471778 [details] The archive contains video with bug and an app to reproduce. Latest iOS/Safari on iPhone 15 Pro Max. When zooming page for some short time, a browser get crashed and not possible to debug/find the reason. Steps: 1. open app attached 2. zoom in/out a bit to increase CPU loading 3. see page crashed https://forum.bryntum.com/viewtopic.php?t=27780&start=70
I got confirmation that this is not about an app but about a webpage.
<rdar://problem/130982413>
Thanks for filing! I've pinged the team about this.
I've opened both of the index.html files inside "advanced" in the zip file, but neither loads content. Please give specific instructions for how to run the attached web content.
Sorry. My mistake. Please use this command to add NPM repo npm config set "@bryntum:registry=https://npm.bryntum.com" Full guide in case of errors https://bryntum.com/products/scheduler/docs/guide/Scheduler/npm-repository In attached app folder "advanced", remove package-lock.json file, in package.json replace the line "@bryntum/scheduler": "5.6.8" with "@bryntum/scheduler-trial": "5.6.8", and after that call npm i npm start Please ping me in case of any questions
(In reply to Alex Lazarev from comment #5) > Sorry. My mistake. > Please use this command to add NPM repo > > npm config set "@bryntum:registry=https://npm.bryntum.com" > > Full guide in case of errors > https://bryntum.com/products/scheduler/docs/guide/Scheduler/npm-repository > > In attached app folder "advanced", remove package-lock.json file, > in package.json replace the line > > "@bryntum/scheduler": "5.6.8" > > with > > "@bryntum/scheduler-trial": "5.6.8", > > and after that call > > npm i > npm start > > Please ping me in case of any questions Is it possible for you to set up the repro case on a server instead? WebKit engineers don't typically run Node projects to investigate. Thanks!
Please find test case here https://dev.bryntum.com/examples/apple-test/ Just verified with iPhone 14 Pro + Safari. I zoomed in/out timeline area with gesture few seconds (5-15 secs). Sometimes it breaks the page in 1-2 seconds, sometimes I need to zooming very fast 10 seconds to get it reproduced.
@Simon Fraser - Have you been able to reproduce the crash using the test case we hosted for you?
I have, thank you. Please leave the test page available for further investigation.
I'm pinging Ryan who might be able to look at this.
Hello! Any news on it guys?
@Simon Fraser Any updates of what might be causing this?
At first glance I think it's the number of layers that get "composited". Use the web inspector Layers tab to view, and keep an eye on the total layer memory use.
Ok, do you mean we should investigate this from the outside? I was under the impression someone on the Webkit team would be looking at this. Can you please open an internal ticket to add better crash messages that can help us web devs correct the possible "over-layering". The current tab crash message helps exactly no one.