Show Summary Details

Page of

PRINTED FROM OXFORD HANDBOOKS ONLINE ( © Oxford University Press, 2018. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Handbooks Online for personal use (for details see Privacy Policy and Legal Notice).

date: 29 November 2020

Abstract and Keywords

On June 29, 1613, at the first performance of William Shakespeare and John Fletcher's All Is True, the Globe playhouse burned to the ground. The destruction of this iconic theatre might be imagined as a conveniently catastrophic mark for the end of an era. But the conflagration led to nothing more than a piece of colorful London news and a substantial expense for the actors who owned the Globe; none of the audience was hurt, and nothing fundamental about the Jacobean theater changed. The Globe was promptly rebuilt, and improved, while the King's Men continued performing in their Blackfriars venue. The King's Men's consolidation of its dominance limited the prospects for the other adult playing companies, and oddly diminished the general level of competition between the London playhouses. This article traces the history of adult playing companies in England for the period 1613–1625. It looks at playhouse repertories, the causal relationship between the decline and the loss of patronage, boy companies, clowning on the Jacobean stage, and the decline of Palatine's Men and Queen Anne's Men.

Keywords: England, adult playing companies, theatre, William Shakespeare, John Fletcher, Globe playhouse, repertories, patronage, boy companies, clowning

Access to the complete content on Oxford Handbooks Online requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can''t find the answer there, please contact us.