Audiotool board archive

Desktop-Only Visual Corruption / Glitch

THall · started 2019-05-28 18:55 · updated 2019-06-14 19:48

Characteristics:

  • Flashing devices
  • Flashing causes 'x-ray' effect where device wireframes are momentarily visible
  • Entire Desktop workspace being corrupted by rectangular MissingNo.-like visual corruption.

Bug appears to be independent of:

  • Window Size: Yes---but changing it to/from fullscreen resets SOME of the corruption
  • Closing the app and opening it again: Yes
  • Device: Haven't tested
  • Track I'm Working On: Yes & No, corruption begins immediately, even before interaction with the interface, even after changing to "Show Desktop & Timeline" removes the corruption. Sometimes whether or not a certain track is open / playing CAN cause corruption to restart, and ALSO affects whether or not "Show Desktop & Timeline" removes corruption effect.
  • Zoom Level & Viewing: Yes & No---Corruption remains in the same area, although sometimes wireframes of various devices appear to be visible.
  • Expanding Timeline / Desktop: Yes, corruption does not show in the timeline but is visible in the same manner when the desktop is brought into view again
  • Using "Show Desktop & Timeline": On certain track using this option removes corruption but does not stop flashing / temporary wireframe 'x-ray' effect. On a certain track it does not
  • Restarting Device: Haven't tested

what have I done

Comments (11)

2019-05-28 20:38 · 2019-05-28

Thanks for all the details. Can you add which Browser+version, OS, Device you are using?
Is it possible to get some screenshots of the glitches? Does it look similar to this report: https://www.audiotool.com/board/bug_reports/new_colorable_wires
If using Chrome: What's the output of chrome://gpu/
Is your graphics driver up to date?

THall · reply
2019-05-29 16:51 · 2019-05-29

Browser was Chrome. I won't be able to add version, OS, and Device at this time as well as any information that would have to be pulled from the device I was on.
The report you added was spot on in that the visual bugs are virtually identical to the ones I had, although the visual corruption wasn't ever as complete as it is in the second photo, it was closer to a random distribution that sometimes would cover a significant percentage of the screen. Beyond that, the glitches appear to be identical to the ones I experienced.
I can confirm that it is dependent on the device, as I opened up the same projects on a completely different device and completed my work without issue.

THall · reply
2019-06-03 18:22 · 2019-06-03

output of chrome://gpu/
Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Hardware accelerated
Out-of-process Rasterization: Disabled
Hardware Protected Video Decode: Unavailable
Rasterization: Hardware accelerated
Skia Renderer: Disabled
Surface Control: Disabled
Surface Synchronization: Enabled
Video Decode: Hardware accelerated
Viz Service Display Compositor: Enabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
add_and_true_to_loop_condition
adjust_src_dst_region_for_blitframebuffer
avoid_stencil_buffers
clamp_texture_base_level_and_max_level
decode_encode_srgb_for_generatemipmap
disable_2d_canvas_auto_flush
disable_framebuffer_cmaa
disable_webgl_rgb_multisampling_usage
dont_use_loops_to_initialize_variables
emulate_abs_int_function
get_frag_data_info_bug
init_two_cube_map_levels_before_copyteximage
max_msaa_sample_count_4
msaa_is_slow
pack_parameters_workaround_with_pack_buffer
rebind_transform_feedback_before_resume
regenerate_struct_names
remove_invariant_and_centroid_for_essl3
reset_teximage2d_base_level
rewrite_texelfetchoffset_to_texelfetch
scalarize_vec_and_mat_constructor_args
set_zero_level_before_generating_mipmap
unfold_short_circuit_as_ternary_operation
unpack_alignment_workaround_with_unpack_buffer
unpack_image_height_workaround_with_unpack_buffer
use_intermediary_for_copy_texture_image
use_unused_standard_shared_blocks
disabled_extension_GL_KHR_blend_equation_advanced
disabled_extension_GL_KHR_blend_equation_advanced_coherent
Problems Detected
Protected video decoding with swap chain is for Windows and Intel only
Disabled Features: protected_video_decode
Unfold short circuit on Mac OS X: 307751
Applied Workarounds: unfold_short_circuit_as_ternary_operation

THall · reply
2019-06-03 18:22 · 2019-06-03

Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
Mac drivers handle struct scopes incorrectly: 403957
Applied Workarounds: regenerate_struct_names
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: msaa_is_slow
glGenerateMipmap fails if the zero texture level is not set on some Mac drivers: 560499
Applied Workarounds: set_zero_level_before_generating_mipmap
Pack parameters work incorrectly with pack buffer bound: 563714
Applied Workarounds: pack_parameters_workaround_with_pack_buffer
Alignment works incorrectly with unpack buffer bound: 563714
Applied Workarounds: unpack_alignment_workaround_with_unpack_buffer
copyTexImage2D fails when reading from IOSurface on multiple GPU types.: 581777
Applied Workarounds: use_intermediary_for_copy_texture_image
Multisample renderbuffers with format GL_RGB8 have performance issues on Intel GPUs.: 607130
Applied Workarounds: disable_webgl_rgb_multisampling_usage
Use GL_INTEL_framebuffer_CMAA on ChromeOS: 535198
Applied Workarounds: disable_framebuffer_cmaa
glGetFragData{Location|Index} works incorrectly on Max: 638340
Applied Workarounds: get_frag_data_info_bug
glResumeTransformFeedback works incorrectly on Intel GPUs: 638514
Applied Workarounds: rebind_transform_feedback_before_resume
Result of abs(i) where i is an integer in vertex shader is wrong: 642227
Applied Workarounds: emulate_abs_int_function
Rewrite texelFetchOffset to texelFetch for Intel Mac: 642605
Applied Workarounds: rewrite_texelfetchoffset_to_texelfetch
Rewrite condition in for and while loops for Intel Mac: 644669
Applied Workarounds: add_and_true_to_loop_condition
Decode and encode before generateMipmap for srgb format textures on macosx: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap

THall · reply
2019-06-03 18:22 · 2019-06-03

Init first two levels before CopyTexImage2D for cube map texture on Intel Mac 10.12: 648197
Applied Workarounds: init_two_cube_map_levels_before_copyteximage
Insert statements to reference all members in unused std140/shared blocks on Mac: 618464
Applied Workarounds: use_unused_standard_shared_blocks
Tex(Sub)Image3D performs incorrectly when uploading from unpack buffer with GL_UNPACK_IMAGE_HEIGHT greater than zero on Intel Macs: 654258
Applied Workarounds: unpack_image_height_workaround_with_unpack_buffer
adjust src/dst region if blitting pixels outside framebuffer on Mac: 644740
Applied Workarounds: adjust_src_dst_region_for_blitframebuffer
Mac driver GL 4.1 requires invariant and centroid to match between shaders: 639760, 641129
Applied Workarounds: remove_invariant_and_centroid_for_essl3
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
Certain Apple devices leak stencil buffers: 713854
Applied Workarounds: avoid_stencil_buffers
Reset TexImage2D base level to 0 on Intel Mac 10.12.4: 705865
Applied Workarounds: reset_teximage2d_base_level
Shader variable initialization in a loop caused perf regression on Mac Intel.: 809422
Applied Workarounds: dont_use_loops_to_initialize_variables
8x MSAA is slow for alpha:false WebGL contexts on Mac Intel: 812071
Applied Workarounds: max_msaa_sample_count_4
glFlush error on Mac: 841755
Applied Workarounds: disable_2d_canvas_auto_flush
Clamp texture's BASE_LEVEL/MAX_LEVEL for GenerateMipmap: 913301
Applied Workarounds: clamp_texture_base_level_and_max_level
Skia renderer is not used by default.
Disabled Features: skia_renderer

THall · reply
2019-06-03 18:24 · 2019-06-03

That's the text-only version of the output of chrome://gpu/, if you want the information in the tables you'll have to let me know

Known As I · reply
2019-06-03 19:51 · 2019-06-03

Ok, seems to be some Mac on Chrome with some Intel GPU. That's most likely the same issue.

THall · reply
2019-06-03 20:37 · 2019-06-03

I thought so, but it didn't hurt to confirm it.

2019-06-04 20:47 · 2019-06-04

THANK YOU SO MUCH!!
It works now :D :D :D

2019-06-05 18:24 · 2019-06-05

Glitches have not reappeared; the issue appears to be resolved, thank you.

anonymous user
2019-06-14 19:48 · 2019-06-14

This ste is slow