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.

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

Stackoverflow Exception when processing ManagedReferenceDocuments #289

Closed
josullivan opened this issue May 4, 2016 · 3 comments
Closed
Assignees

Comments

@josullivan
Copy link

Unable to build the doc site for a single project even though YAML files are being generated

Minimal repro steps:

  1. Download, install and initialize Docfx 1.8 (but also happens with 1.7.x)
  2. Point at single project in local Git repo in docfx.json
  3. Run docfx spagent/docfx.json --serve

Expected to see the documentation site available at http://localhost:8080

Instead see a Stackoverflow Exception when building:
Info: [Build Document.TocDocumentProcessor]Building 3 file(s) in TocDocumentProcessor(BuildTocDocument)...
Info: [Build Document.ManagedReferenceDocumentProcessor]Building 134 file(s) in ManagedReferenceDocumentProcessor(BuildM
anagedReferenceDocument=>ApplyOverwriteDocumentForMref=>FillReferenceInformation)...

Process is terminated due to StackOverflowException in mscorlib.

A significant number of YAML docs are created in the api folder but no html docs generated

@vicancy
Copy link
Contributor

vicancy commented May 6, 2016

Any chance for us to take a look at a repo that can repro the issue?

@josullivan
Copy link
Author

Took us a while to get minimal repro as below where circular references cause this StackOverflowException.
`

  public class Program
  {
        static void Main(string[] args)
       {

       }

       /// <seealso cref="Program.B"/>
       public int A()
       {
          return 0;
       }

       /// <seealso cref="Program.A"/>
       public int B()
       {
           return 0;
       }
  }

`

@superyyrrzz
Copy link
Contributor

@josullivan It has been fixed in DocFX 1.9.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants