[prettify] Performance degradation for minified code in firefox developer edition

UNCONFIRMED
Unassigned

Status

UNCONFIRMED
2 years ago
2 months ago

People

(Reporter: matt, Unassigned)

Tracking

54 Branch

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170313004011

Steps to reproduce:

Have a codebase that isnt the most efficient in the world, but works fine on a decent machine. Pre-minification, everything works at roughly the same level of performance on chrome / firefox stable / firefox developer branch. Post minification that isnt the case.

You can see the minified version here http://custom.gelaskins.com/312 upload a decent resolution image, and drag it around. You will notice (on a decent machine) you get substancially lower frame rate on FF developer edition.

Originally opened this on the create-react-app bug tracker https://github.com/facebookincubator/create-react-app/issues/1809


Actual results:

Post minification there is a serious performance degradation for firefox developer edition. This is not present in firefox stable, or in chrome stable.


Expected results:

I would expect the same performance characteristics pre and post minification.

Updated

a year ago
Component: Untriaged → Developer Tools
Summary: Performance degradation for minified code in firefox developer edition → [prettify] Performance degradation for minified code in firefox developer edition
Component: Developer Tools → Developer Tools: Debugger
Thanks :matt, can you explain how you're minifying your code? Are you using the debugger to prettify the code or are you minifying the code with a build step?
(Reporter)

Comment 2

a year ago
:jlast webpack / uglify. I am using create-react-app from facebook (https://github.com/facebookincubator/create-react-app) to do the minification (if you want to look at exact settings)

Updated

2 months ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.