Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Crash when changing between mesh preview tabs with no capture loaded #1

Closed
baldurk opened this issue Feb 27, 2014 · 2 comments
Closed

Crash when changing between mesh preview tabs with no capture loaded #1

baldurk opened this issue Feb 27, 2014 · 2 comments
Labels
Bug A crash, misbehaviour, or other problem

Comments

@baldurk
Copy link
Owner

baldurk commented Feb 27, 2014

Reported via the anonymous crash submission tool. When you don't have a capture loaded in the UI, changing between the mesh preview tabs crashes the application.
@baldurk
Copy link
Owner Author

baldurk commented Feb 27, 2014

Fixed very simply, fix will be in the next release.

@baldurk baldurk closed this as completed Feb 27, 2014
@baldurk baldurk added this to the Release v0.19 milestone Mar 1, 2014
@baldurk
Copy link
Owner Author

baldurk commented Mar 1, 2014

Changed my workflow slightly - while the source isn't public I'm going to leave bugs that aren't fixed in a released build yet open until the next release, but ad an appropriate label.

@baldurk baldurk reopened this Mar 1, 2014
@baldurk baldurk closed this as completed Mar 14, 2014
baldurk added a commit that referenced this issue Feb 16, 2016
@baldurk
[Sparse #1] Track memory referencing of sparse resources into queues
702f487 
* Normal resources have a single memory bind that can be added to frame
  references when the resource is. Sparse resources don't have that easy
  single mapping.
* Calls to MarkResourceFrameReferenced with a 0 ResourceId aren't a
  real problem, but we have to be careful when dirtying resources.
* We don't have to dirty memory that's sparsely bound as we'll dirty it
  as soon as its sparsely bound. We do have to worry about making sure
  that memory is correctly frame referenced.
* To do this command buffers track the sparsemapping structures (will be
  created for all sparse resources) that are referenced underneath them.
  Then at queue submit time the current sparse mapping is iterated and
  all bound memory marked frame referenced.
* For most cases where a buffer is bound or similar, we can directly add
  the sparsemapping from the resource record. For descriptor sets we
  must do this indirectly - by marking any bindframerefs in the descset
  record with a bit indicating that the associated resource is sparse,
  then at submit time when iterating the bindframerefs, taking any with
  the bit set and looking up its record to find the sparsemapping.
@kbiElude kbiElude mentioned this issue Feb 23, 2016
Closed
@kbiElude kbiElude mentioned this issue Mar 1, 2016
Closed
@jshofmann jshofmann mentioned this issue Jun 9, 2016
Closed
@Vtec234 Vtec234 mentioned this issue May 14, 2017
Closed
@Yours3lf Yours3lf mentioned this issue Jul 7, 2017
Closed
@airlied airlied mentioned this issue Nov 20, 2017
Closed
@kvark kvark mentioned this issue Jan 22, 2018
Closed
@MaikelChan MaikelChan mentioned this issue Feb 6, 2018
Closed
@baldurk baldurk mentioned this issue Mar 13, 2018
Closed
@bradc6 bradc6 mentioned this issue Jun 22, 2018
Closed
@penguin42 penguin42 mentioned this issue Nov 9, 2018
Closed
@darksylinc darksylinc mentioned this issue Apr 15, 2019
Closed
@Jiboo Jiboo mentioned this issue Jun 30, 2019
Closed
@mimijava mimijava mentioned this issue Jul 4, 2019
Closed
@Raikiri Raikiri mentioned this issue Oct 7, 2019
Closed
@pengfei666 pengfei666 mentioned this issue Dec 11, 2019
Closed
@jullej jullej mentioned this issue Jan 28, 2020
Closed
This was referenced Feb 4, 2020
Closed
Closed
@kvark kvark mentioned this issue May 2, 2020
Closed
@vk2gpu vk2gpu mentioned this issue Jul 8, 2020
Closed
@eaglefly628 eaglefly628 mentioned this issue Jul 19, 2021
Closed
@Oribow Oribow mentioned this issue Feb 20, 2022
Closed
CamilliaX pushed a commit to CamilliaX/renderdoc that referenced this issue Aug 14, 2023
@CamilliaX
baldurk#1
e3d2f20
@xjqxzyr xjqxzyr mentioned this issue Aug 23, 2023
Closed
@wtmilk wtmilk mentioned this issue Dec 6, 2023
Closed
@haasn haasn mentioned this issue Feb 19, 2024
Closed
@ccosse ccosse mentioned this issue Jun 8, 2024
Closed
@shmadchenko shmadchenko mentioned this issue Jul 8, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug A crash, misbehaviour, or other problem
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@baldurk