New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Re)Drawing issue #705

Closed
stevejalim opened this Issue Sep 2, 2014 · 86 comments

Comments

Projects
None yet
@stevejalim

stevejalim commented Sep 2, 2014

TLDR: after a while, Postman seems to stop rendering the UI properly

Hard to pin this down, but it seems that when the packaged Postman has been running for while, it is less and less likely to properly redraw the interface, usually requiring a manual window resize to show elements. This may or may not be related to the fact it's running in the ultra-crazy max Retina res on my Mac.

Here endeth the world's most useless bug report.

@stevejalim stevejalim changed the title from (Re)Drawing issue when open for a while to (Re)Drawing issue Sep 2, 2014

@abhijitkane

This comment has been minimized.

Member

abhijitkane commented Sep 3, 2014

I've faced the same problem with Postman, as well as normal websites in Chrome. Parts of the page randomly disappear, and resizing the window solves it. Not sure what to do about it, thought.

@stevejalim

This comment has been minimized.

stevejalim commented Sep 3, 2014

Are you on a Retina display, too?

On 3 September 2014 07:10, Abhijit Kane notifications@github.com wrote:

I've faced the same problem with Postman, as well as normal websites in
Chrome. Parts of the page randomly disappear, and resizing the window
solves it. Not sure what to do about it, thought.


Reply to this email directly or view it on GitHub
#705 (comment)
.

@abhijitkane

This comment has been minimized.

Member

abhijitkane commented Sep 3, 2014

Yes, I've seen others face the issue as well.

@a85 a85 added the Bug label Sep 5, 2014

@bryannaegele

This comment has been minimized.

bryannaegele commented Sep 7, 2014

I am seeing this, too. Retina display, Chrome 37. Seeing it on Mac, as well as Windows 8 Chrome 37 running in Parallels 10.

@adamup928

This comment has been minimized.

adamup928 commented Sep 7, 2014

Same here - retina display, Chrome 37 on Mac OS X Mavericks.

@abhijitkane

This comment has been minimized.

Member

abhijitkane commented Sep 8, 2014

Are you seeing this issue on Postman only, or do you see it with websites as well?

@adamup928

This comment has been minimized.

adamup928 commented Sep 8, 2014

Postman only.

On Sunday, September 7, 2014, Abhijit Kane notifications@github.com wrote:

Are you seeing this issue on Postman only, or do you see it with websites
as well?


Reply to this email directly or view it on GitHub
#705 (comment)
.

@stevejalim

This comment has been minimized.

stevejalim commented Sep 8, 2014

Am only using packaged Postman and seeing it there. Chrome 37 itself of
perfect.

Def seems to be worse when there are more saved scenarios/collections -
anecdotal but poss helpful
On 8 Sep 2014 04:58, "adamup928" notifications@github.com wrote:

Postman only.

On Sunday, September 7, 2014, Abhijit Kane notifications@github.com
wrote:

Are you seeing this issue on Postman only, or do you see it with
websites
as well?


Reply to this email directly or view it on GitHub
<
https://github.com/a85/POSTMan-Chrome-Extension/issues/705#issuecomment-54773729>

.


Reply to this email directly or view it on GitHub
#705 (comment)
.

@JakeWorrell

This comment has been minimized.

JakeWorrell commented Sep 8, 2014

I'd just like to add a "Me too" here. I'm also on Retina MBP and I find that I can force the interface to redraw by clicking any of the 'edit'. buttons in the sidebar (e.g. 'edit collection' or any of the buttons to rename folders) as a workaround.

@a85

This comment has been minimized.

a85 commented Sep 8, 2014

Is this happening after a specific date or been happening in the packaged app since the beginning?

@adamup928

This comment has been minimized.

adamup928 commented Sep 8, 2014

Packaged app since the beginning for me. I switched from the extension,
imported a bunch of collections, and this problem started occurring.

Dragging my mouse over blank areas where various elements should
be sometimes causes them to redraw. Submitting a request (the submit button
is always visible) always triggers a successful redraw.

On Monday, September 8, 2014, Abhinav Asthana notifications@github.com
wrote:

Is this happening after a specific date or been happening in the packaged
app since the beginning?


Reply to this email directly or view it on GitHub
#705 (comment)
.

@a85

This comment has been minimized.

a85 commented Sep 8, 2014

@abhijitkane

This comment has been minimized.

Member

abhijitkane commented Sep 8, 2014

  1. For me, it happens only when I've connected an external display and am using both. Don't remember seeing the issue without the display connected.
  2. The frequency of the problem increases as Chrome is left open.
  3. I've seen the issue on websites as well - not just Postman.

Somewhat related issues with mac/chrome/retina:
https://code.google.com/p/chromium/issues/detail?id=383261
https://code.google.com/p/macvim/issues/detail?id=429

This describes my problem perfectly:
https://code.google.com/p/chromium/issues/detail?id=324691

@stevejalim

This comment has been minimized.

stevejalim commented Sep 8, 2014

FWIW, I've had it on laptop-screen-only too.

Not seen it at all on websites

@adamup928

This comment has been minimized.

adamup928 commented Sep 8, 2014

Laptop-screen (only) has shown these issues for me, as well. No similar
problems on any other websites.

Tried another packaged app (Chrome Dev Editor) and it worked without issue.
I had a couple dozen files open, and edited in it for a bit. No drawing
errors.

On Mon, Sep 8, 2014 at 10:53 AM, Steve Jalim notifications@github.com
wrote:

FWIW, I've had it on laptop-screen-only too.

Not seen it at all on websites


Reply to this email directly or view it on GitHub
#705 (comment)
.

@abhijitkane

This comment has been minimized.

Member

abhijitkane commented Sep 8, 2014

Sample screenshot: screenshot 2014-09-08 09 42 17

@JakeWorrell

This comment has been minimized.

JakeWorrell commented Sep 8, 2014

I have been experiencing this for the last 4 weeks at least, I can't remember if it was always the case as I have not been using the packaged app for very long

@skuppa

This comment has been minimized.

skuppa commented Sep 8, 2014

I am having the same issue, please look at the screenshot.
screen shot 2014-09-08 at 9 33 34 am

@abhijitkane

This comment has been minimized.

Member

abhijitkane commented Sep 8, 2014

@skuppa @JakeWorrell @adamup928 @stevejalim
Do you remember what you clicked on? I'm only seeing the issue when I click on Pretty mode button and the cookies tab.

@abhijitkane

This comment has been minimized.

@adamup928

This comment has been minimized.

adamup928 commented Sep 8, 2014

The issue is reliably reproduced when I click the pretty mode button or cookies tab, but previously (can't seem to reproduce it right now), it also happened when I switched between saved requests.

@JakeWorrell

This comment has been minimized.

JakeWorrell commented Sep 8, 2014

This tends to happen to me when I switch between saved requests. It seems to be intermittent unfortunately

@fherrerac

This comment has been minimized.

fherrerac commented Sep 10, 2014

Does anybody know if it's possible to get a previous Chrome/POSTMAN version without this issue while this is investigated/fixed ?

@abhijitkane

This comment has been minimized.

Member

abhijitkane commented Sep 10, 2014

Not that I know of. The only way to install an older version would be from the source. AFAIK, the legacy app (https://chrome.google.com/webstore/detail/postman-rest-client/fdmmgilgnpjigdojojpjoooidkmcomcm?hl=en) does not have this problem, but that would mean losing a lot of features of the packaged app.

@fherrerac

This comment has been minimized.

fherrerac commented Sep 10, 2014

I see. Too bad, this is making dev work hard :-s. Hopefully, this gets resolved soon.

@stevejalim

This comment has been minimized.

stevejalim commented Sep 10, 2014

Question for all: does it seem to happen when only using the lower-powered
graphics-card mode? Anecdotally, that may be the case for me, but I'd need
to test extensively.

@JakeWorrell

This comment has been minimized.

JakeWorrell commented Sep 10, 2014

I have experienced this when a second monitor is attached on many occasions. When a second monitor is attached I believe that forces discreet graphics.

@fherrerac

This comment has been minimized.

fherrerac commented Sep 12, 2014

Fyi, today was still seeing the issue. I closed and reopened the left pane/column with endpoints. That seems to have helped, at least for now. Might want to try it and see.

@lawrencejones

This comment has been minimized.

lawrencejones commented Nov 20, 2014

Also having this issue on a Chrome 39 build, after fresh installing postman. This is really killing the app for me, it makes it entirely unusable :(

Video here for anyone who doesn't have a retina device.

@geoidesic

This comment has been minimized.

geoidesic commented Nov 25, 2014

This happens to me to. Mine is a retina macbook pro with latest Chrome on Yosemite (but was happening before I upgraded OS too). It happens repeatably:

1.Click on an item in a collection to load the settings e.g. a POST request with parameters an headings.
2. Paste in a new URL instead of the loaded one.
3. Mouse over various bits of the UI ending with mouse-over the SEND button.
4. Click another item in the same collection to load the settings e.g. a GET request with a different URL.

I've tried that same sequence 5 times in a row and each time the rendering breaks after step 4.

@vladvino

This comment has been minimized.

vladvino commented Nov 25, 2014

Same here. I wasn't able to use the app for a month or even more now. When is it going to be fixed?!

@monowai

This comment has been minimized.

monowai commented Nov 25, 2014

This is an inconvenience, not a showstopper. If you click the environments dropdown it will redraw enough of the screen to reveal the URL box which you can then click in to complete the redraw of the top half of the screen. This should also reveal the buttons - if any remain hidden, then move the mouse over where they should be and they reappear.

@lawrencejones

This comment has been minimized.

lawrencejones commented Nov 25, 2014

Mine doesn't redraw much when this is toggled, and I'd disagree. The whole point of this tool is convenience and ease of use; when you can't see half the screen, it's definitely a show stopper.

@geoidesic

This comment has been minimized.

geoidesic commented Nov 25, 2014

Inconvenient tools are not those a professional should be using.

@pbellchambers

This comment has been minimized.

pbellchambers commented Nov 28, 2014

Just a note that I get this on a windows machine (with a resolution similar to a mac retina display... 2880x1620). Is this just a general problem chrome has with display scaling?

@abhijitkane

This comment has been minimized.

Member

abhijitkane commented Dec 5, 2014

This is the first time someone has reported this issue with Windows. Guess it's not a Mac-specific problem then.
The latest version of Postman (1.0.2) has some CSS "fixes" that do appear to reduce the problem a bit, though.

@Aidenir

This comment has been minimized.

Aidenir commented Dec 5, 2014

Im getting this on Ubuntu as well. In using dell precision m3800 which has a resolution the same as the mbp I think. but I have the resolution set to 1080p and using an external 1080p monitor.

@sebastiaanluca

This comment has been minimized.

sebastiaanluca commented Dec 17, 2014

Also been battling this issue for a few months now. Really annoying to say the least :) Have to resize the window after every request, which is a lot.

@a85

This comment has been minimized.

a85 commented Jan 3, 2015

Sorry for the inconvenience caused people. We are as frustrated as everyone else.

Posted updates on Chromium's bug tracker:
https://code.google.com/p/chromium/issues/detail?id=412414
https://code.google.com/p/chromium/issues/detail?id=412299

We'll try to change the DOM structure and see if that helps in going around this problem.

@abhijitkane

This comment has been minimized.

Member

abhijitkane commented Jan 15, 2015

We've made a few CSS changes on the staging version - https://chrome.google.com/webstore/detail/postman-rest-client-packa/mgicbpdmnpnfckafakeoiomkjcplfcld/

It appears to have reduced the problem to a great extent. @Quagh @Aidenir @pbellchambers can you check it out and see if the problem has improved?

@pbellchambers

This comment has been minimized.

pbellchambers commented Jan 15, 2015

Still happening for me, frequency seems about the same (it is intermittent however, but was always that way).

Chrome:

Version 39.0.2171.95 m

POSTMan:

Version 1.0.5 (packaged)
OS: win
Architecture: x86-32
Native client architecture: x86-64

untitled

@a85

This comment has been minimized.

a85 commented Jan 15, 2015

@pbellchambers Is that after using Postman for some time or almost instantly after sending a request?

@pbellchambers

This comment has been minimized.

pbellchambers commented Jan 15, 2015

After sending a request and then switching to another request. I can reproduce it right after opening postman.

@a85

This comment has been minimized.

a85 commented Jan 15, 2015

Weird. I don't see it that often on my Retina machine even at the highest resolution. We suspect it might be something to do with the scrollbar code that we are using. Will push another version on the staging app soon.

@sebastiaanluca

This comment has been minimized.

sebastiaanluca commented Jan 15, 2015

I can also reproduce when sending a request and switching views.

Just had a weird thing though. So I'm on a MacBook Pro retina and tried reproducing the bug. The bug occurred, and the view was glitched as expected. Suddenly my graphics card switched from the more powerful nVidia one, to the integrated Intel graphics card… and the view reset itself, showing everything again. Maybe something to look into, check if it's related?

@a85 a85 added the Performance label Jan 20, 2015

@shamasis

This comment has been minimized.

Member

shamasis commented Jan 20, 2015

We made some more change to combat this issue. It appears to us as something to do with the overflow characteristics of scrollable elements.

:shipit: The beta is now available:

https://chrome.google.com/webstore/detail/postman-rest-client-packa/mgicbpdmnpnfckafakeoiomkjcplfcld (version: 1.0.6.3)

Your inputs pushed us in a direction to force better buffered 3D acceleration on erring elements. Following that, we are not seeing the issue anymore (at least not in past 8 hours.)

Thanks to everybody for helping. @Quagh @Aidenir @pbellchambers and others, could you share your experience with this release? We will keep on trying until we see this through.

@Zajn

This comment has been minimized.

Zajn commented Jan 20, 2015

I had been encountering this issue as well, but so far using Postman 1.0.6.3, I have not seen it occur yet.

OS: OSX 10.10
Postman: 1.0.6.3
Chromium: 38.0.2125.122 (290379)

@rtuin

This comment has been minimized.

rtuin commented Jan 20, 2015

Thanks for your efforts, i will give it a try and let you know!

Op 20 jan. 2015 om 19:19 heeft Shamasis Bhattacharya notifications@github.com het volgende geschreven:

We made some more changes to combat this issue. It appears to us as something to do with the overflow characteristics of scrollable elements.

The beta is now available:

https://chrome.google.com/webstore/detail/postman-rest-client-packa/mgicbpdmnpnfckafakeoiomkjcplfcld (version: 1.0.6.3)

Your inputs pushed us in a direction to force better buffered 3D acceleration on erring elements. Following that, we are not seeing the issue anymore (at least in the last 8 hours.)

Thanks to everybody for helping. @Quagh @Aidenir @pbellchambers and others, could you share your experience with this release? We will keep on trying until we see this through.


Reply to this email directly or view it on GitHub.

@skuppa

This comment has been minimized.

skuppa commented Jan 20, 2015

It works great so far and I was not able reproduce the issue. Great work.

-Sridharan

On Tue, Jan 20, 2015 at 10:37 AM, Zajn notifications@github.com wrote:

I had been encountering this issue as well, but so far using Postman
1.0.6.3, I have not seen it occur yet.

OS: OSX 10.10
Postman: 1.0.6.3
Chromium: 38.0.2125.122 (290379)


Reply to this email directly or view it on GitHub
#705 (comment)
.

@sebastiaanluca

This comment has been minimized.

sebastiaanluca commented Jan 20, 2015

Seems to work :)

@rtuin

This comment has been minimized.

rtuin commented Jan 20, 2015

Amazing, work. Been working with the beta for a over an hour without having the redraw problem! 👍

@fherrerac

This comment has been minimized.

fherrerac commented Jan 20, 2015

This beta seems to fix the issue, but doesn't allow to sign in and thus test fully using jetpacks. When do you expect to release it so can be tested signing in w/jetpacks ?

@a85

This comment has been minimized.

a85 commented Jan 21, 2015

Thank you everyone for the confirmation. We'll be pushing an update on the production channel today.

@mikemwalsh

This comment has been minimized.

mikemwalsh commented Jan 22, 2015

YES! I finally got off my butt to see if this was a common issue, read the entire issue log and made it to the end saying a fix is heading to production! Thanks - cant wait to update to it!

@shamasis

This comment has been minimized.

Member

shamasis commented Jan 28, 2015

We are truly happy that we could finally get to the bottom this issue. I'm closing this issue with a postmortem of it on our blog - Chrome Repaint Issue.

:shipit: The changes have been merged with our production app version 1.0.6.

Thanks to all for helping. In the unlikely event that you are still facing this issue, let us know on this thread.

@shamasis shamasis closed this Jan 28, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment