mirror of
https://github.com/trezor/trezor-firmware.git
synced 2025-01-09 15:00:58 +00:00
e0b4cab2db
For reasons unknown, a previous homescreen layout can sometimes survive a GC cycle in main's unimport loop. Two homescreen layouts can't exist simultaneously, so creating a new one would fail. It _seems_ that after restarting the session, the homescreen object still exists but is not reachable anymore, so a second GC cycle properly disposes of it. So what we do is simply catch the possible MemoryError, invoke GC explicitly, and try again. |
||
|---|---|---|
| .clusterfuzzlite | ||
| .github | ||
| ci | ||
| common | ||
| core | ||
| crypto | ||
| docs | ||
| legacy | ||
| python | ||
| rust | ||
| storage | ||
| tests | ||
| tools | ||
| vendor | ||
| .clang-format | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| .pylintrc | ||
| .yamllint.yml | ||
| build-docker.sh | ||
| CODEOWNERS | ||
| COMMITS.md | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| create_monorepo.py | ||
| LICENSE.md | ||
| Makefile | ||
| poetry.lock | ||
| poetry.toml | ||
| pyproject.toml | ||
| README.md | ||
| SECURITY.md | ||
| setup.cfg | ||
| shell.nix | ||
Trezor Firmware
Repository Structure
ci: Gitlab CI configuration filescommon/defs: JSON coin definitions and support tablescommon/protob: Common protobuf definitions for the Trezor protocolcommon/tools: Tools for managing coin definitions and related datacore: Trezor Core, firmware implementation for Trezor Tcrypto: Stand-alone cryptography library used by both Trezor Core and the Trezor One firmwaredocs: Assorted documentationlegacy: Trezor One firmware implementationpython: Python client library and thetrezorctlcommandstorage: NORCOW storage implementation used by both Trezor Core and the Trezor One firmwaretests: Firmware unit test suitetools: Miscellaneous build and helper scriptsvendor: Submodules for external dependencies
Contribute
See CONTRIBUTING.md.
Using Conventional Commits is strongly recommended and might be enforced in future.
Also please have a look at the docs, either in the docs folder or at docs.trezor.io before contributing. The misc chapter should be read in particular because it contains some useful assorted knowledge.
Security vulnerability disclosure
Please report suspected security vulnerabilities in private to security@satoshilabs.com, also see the disclosure section on the Trezor.io website. Please do NOT create publicly viewable issues for suspected security vulnerabilities.
Documentation
See the docs folder or visit docs.trezor.io.